From: "David S. Miller" <davem@davemloft.net>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: James.Bottomley@steeleye.com, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] unify semaphore implementations
Date: Thu, 28 Apr 2005 11:53:44 -0700 [thread overview]
Message-ID: <20050428115344.4e10a7f4.davem@davemloft.net> (raw)
In-Reply-To: <20050428185956.GD16545@kvack.org>
On Thu, 28 Apr 2005 14:59:56 -0400
Benjamin LaHaise <bcrl@kvack.org> wrote:
> On Thu, Apr 28, 2005 at 11:48:09AM -0700, James Bottomley wrote:
> > Could you come up with a less monolithic way to share this so that we
> > can still do a spinlock semaphore implementation instead of an atomic op
> > based one?
>
> As I read the code, it doesn't make a difference: parisc will take a
> spin lock within the atomic operation and then release it, which makes
> the old fast path for the semaphores and the new fast path pretty much
> equivalent (they both take and release one spinlock).
I think parisc should be allowed to choose their implementation of
semaphores. Look, if you change semaphores in some way it will
be their problem to keep their parisc version in sync.
Or you could provide both a spinlocked and an atomic op based implementation
of generic semaphores, as we do for rwsem already.
next prev parent reply other threads:[~2005-04-28 18:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 18:29 [RFC] unify semaphore implementations Benjamin LaHaise
2005-04-28 18:48 ` James Bottomley
2005-04-28 18:59 ` Benjamin LaHaise
2005-04-28 18:53 ` David S. Miller [this message]
2005-04-28 22:40 ` Russell King
2005-04-29 0:42 ` Trond Myklebust
2005-04-29 1:26 ` Paul Mackerras
2005-04-28 22:54 ` David Howells
2005-04-29 0:44 ` Paul Mackerras
2005-04-29 5:33 ` Richard Henderson
2005-04-29 14:14 ` Benjamin LaHaise
2005-04-29 15:42 ` Trond Myklebust
2005-04-30 1:45 ` Paul Mackerras
2005-04-30 5:13 ` Paul Mackerras
2005-04-30 16:40 ` Trond Myklebust
2005-04-30 1:49 ` Paul Mackerras
2005-04-30 16:50 ` Trond Myklebust
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=20050428115344.4e10a7f4.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=James.Bottomley@steeleye.com \
--cc=bcrl@kvack.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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