From: Dipankar Sarma <dipankar@in.ibm.com>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: linux-kernel@vger.kernel.org,
Al Viro <viro@parcelfarce.linux.theplanet.co.uk>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [rfc: patch 0/6] scalable fd management
Date: Wed, 1 Jun 2005 18:20:57 +0530 [thread overview]
Message-ID: <20050601125056.GA4853@in.ibm.com> (raw)
In-Reply-To: <20050601112520.GD20782@holomorphy.com>
On Wed, Jun 01, 2005 at 04:25:20AM -0700, William Lee Irwin III wrote:
> On Mon, May 30, 2005 at 04:20:42PM +0530, Dipankar Sarma wrote:
> > I would appreciate if someone tests this on an arch without
> > cmpxchg (sparc32??). I intend to run some more tests
> > with preemption enabled and also on ppc64 myself.
>
> sparc32 SMP is not going to be a good choice for this. By and large
> ll/sc -style architectures don't have explicit cmpxchg instructions so
> ppc64 at least nominally fits the bill. SMP Alpha testing may also be
> enlightening (as usual).
Actually, I was talking about cmpxchg() primitive in the kernel,
not necessarily the instruction. ppc64 has a cmpxchg() primitive
based on LL/SC. For the archs that do not have cmpxchg(),
rcuref_inc_lf() uses a hashed lock to serialize the reference
count updates. It would be nice to see that code get a spin
on real hardware. AFAICS, sparc32 fits the bill.
Thanks
Dipankar
prev parent reply other threads:[~2005-06-01 12:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-30 10:50 [rfc: patch 0/6] scalable fd management Dipankar Sarma
2005-05-30 10:52 ` [rfc: patch 1/6] Fix rcu initializers Dipankar Sarma
2005-05-30 10:55 ` [rfc: patch 2/6] rcuref APIs Dipankar Sarma
2005-05-30 10:57 ` [rfc: patch 3/6] Break up files struct Dipankar Sarma
2005-05-30 10:58 ` [rfc: patch 4/6] files struct with rcu Dipankar Sarma
2005-05-30 10:59 ` [rfc: patch 5/6] lock free fd lookup Dipankar Sarma
2005-05-30 11:00 ` [rfc: patch 6/6] files locking doc Dipankar Sarma
2005-06-01 11:25 ` [rfc: patch 0/6] scalable fd management William Lee Irwin III
2005-06-01 12:50 ` Dipankar Sarma [this message]
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=20050601125056.GA4853@in.ibm.com \
--to=dipankar@in.ibm.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
--cc=wli@holomorphy.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.