Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755342AbZJRWCn (ORCPT ); Sun, 18 Oct 2009 18:02:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753440AbZJRWCm (ORCPT ); Sun, 18 Oct 2009 18:02:42 -0400 Received: from tomts36-srv.bellnexxia.net ([209.226.175.93]:49761 "EHLO tomts36-srv.bellnexxia.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752805AbZJRWCm (ORCPT ); Sun, 18 Oct 2009 18:02:42 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AsYEALAt20pMRK1g/2dsb2JhbACBUtdghDEE Date: Sun, 18 Oct 2009 18:02:43 -0400 From: Mathieu Desnoyers To: Pavel Machek Cc: Pierre-Marc Fournier , Jan Blunck , Steven Munroe , rp@svcs.cs.pdx.edu, Josh Triplett , linux-kernel@vger.kernel.org, ltt-dev@lists.casi.polymtl.ca, Pierre Habouzit , Jon Bernard , "Paul E. McKenney" , Bert Wesarg Subject: Re: [rp] Userspace RCU 0.2.3 Message-ID: <20091018220243.GA32405@Krystal> References: <20091014223657.GC6458@Krystal> <20091015000225.GG6763@linux.vnet.ibm.com> <20091015023925.GA27959@Krystal> <20091015090042.GA7677@feather> <4AD75EA6.8080809@polymtl.ca> <20091017171615.GD1526@ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: <20091017171615.GD1526@ucw.cz> X-Editor: vi X-Info: http://krystal.dyndns.org:8080 X-Operating-System: Linux/2.6.27.31-grsec (i686) X-Uptime: 18:01:08 up 61 days, 8:50, 3 users, load average: 0.94, 0.55, 0.50 User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1612 Lines: 45 * Pavel Machek (pavel@ucw.cz) wrote: > On Thu 2009-10-15 13:40:54, Pierre-Marc Fournier wrote: > > Josh Triplett wrote: > > > > > > Even Debian has given up on real 386 systems at this point, primarily > > > because system libraries like glibc have; 486 and better represents the > > > bare minimum required at this point. I don't know of any distributions > > > supporting real 386 systems at this point, and doing so would represent > > > a major undertaking. > > > > > > > What about embedded systems? Anyone know if some 386 chips, perhaps even > > in smp configurations, are still in use in those? > > smp 386: definitely not. Hrm, so for UP 386, I wonder what's the best approach. One would be to encapsulate all write accesses to the RCU pointers. If we detect that the architecture lacks cmpxchg, _all_ update operations (rcu_assign_pointer, rcu_xchg_pointer and rcu_cmpxchg_pointer) would have to use the signal-disabled+mutex fall-back. Does it make sense ? Mathieu > > -- > (english) http://www.livejournal.com/~pavelmachek > (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html > > _______________________________________________ > rp mailing list > rp@svcs.cs.pdx.edu > http://svcs.cs.pdx.edu/mailman/listinfo/rp -- Mathieu Desnoyers OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/