From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Pavel Machek <pavel@ucw.cz>
Cc: Pierre-Marc Fournier <pierre-marc.fournier@polymtl.ca>,
Jan Blunck <jblunck@suse.de>,
Steven Munroe <munroesj@linux.vnet.ibm.com>,
rp@svcs.cs.pdx.edu, Josh Triplett <josh@joshtriplett.org>,
linux-kernel@vger.kernel.org, ltt-dev@lists.casi.polymtl.ca,
Pierre Habouzit <madcoder@debian.org>,
Jon Bernard <jbernard@debian.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Bert Wesarg <bert.wesarg@googlemail.com>
Subject: Re: [rp] Userspace RCU 0.2.3
Date: Sun, 18 Oct 2009 18:02:43 -0400 [thread overview]
Message-ID: <20091018220243.GA32405@Krystal> (raw)
In-Reply-To: <20091017171615.GD1526@ucw.cz>
* 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
next prev parent reply other threads:[~2009-10-18 22:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 22:36 Userspace RCU 0.2.3 Mathieu Desnoyers
2009-10-15 0:02 ` Paul E. McKenney
2009-10-15 2:39 ` Mathieu Desnoyers
2009-10-15 4:34 ` Paul E. McKenney
2009-10-15 9:00 ` Josh Triplett
2009-10-15 17:40 ` Pierre-Marc Fournier
2009-10-17 17:16 ` Pavel Machek
2009-10-18 22:02 ` Mathieu Desnoyers [this message]
2009-10-18 22:52 ` [rp] " Pavel Machek
2009-10-18 23:16 ` [ltt-dev] " Mathieu Desnoyers
2009-10-19 23:59 ` Userspace RCU 0.2.4 Mathieu Desnoyers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091018220243.GA32405@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=bert.wesarg@googlemail.com \
--cc=jbernard@debian.org \
--cc=jblunck@suse.de \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltt-dev@lists.casi.polymtl.ca \
--cc=madcoder@debian.org \
--cc=munroesj@linux.vnet.ibm.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=pavel@ucw.cz \
--cc=pierre-marc.fournier@polymtl.ca \
--cc=rp@svcs.cs.pdx.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox