From: Andi Kleen <ak@suse.de>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: thoughts on potential cleanup of semaphores?
Date: 16 Oct 2006 15:46:13 +0200 [thread overview]
Message-ID: <p73slhocr16.fsf@verdi.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0610101025080.8855@localhost.localdomain>
"Robert P. J. Day" <rpjday@mindspring.com> writes:
> after submitting one patch related to semaphores and before i submit
> any others, any thoughts whether any of the following clean-ups are
> valid and/or worthwhile? (some are admittedly simply aesthetic but
> better aesthetics is never a bad thing.)
Semaphores and rwsems need a lot of cleanup. Some time ago we put
spinlocks which are a lot more time critical than semaphores
out of line. So the same could be done for semaphores too. This
had the advantages that most of the assembler voodoo wouldn't
be needed anymore and they could be simple straight C implementations
shared by all architectures.
-Andi
prev parent reply other threads:[~2006-10-16 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 16:00 thoughts on potential cleanup of semaphores? Robert P. J. Day
2006-10-11 2:42 ` Steven Rostedt
2006-10-11 9:34 ` Robert P. J. Day
2006-10-11 14:54 ` Steven Rostedt
2006-10-16 13:46 ` Andi Kleen [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=p73slhocr16.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox