From: Matthew Wilcox <matthew@wil.cx>
To: linux-kernel@vger.kernel.org
Cc: sfr@canb.auug.org.au, lenb@kernel.org, dhowells@redhat.com,
peterz@infradead.org, mingo@elte.hu, harvey.harrison@gmail.com
Subject: Updated generic semaphore patch set
Date: Fri, 14 Mar 2008 14:42:48 -0600 [thread overview]
Message-ID: <20080314204248.GV613@parisc-linux.org> (raw)
I've pushed out a new version of the semaphore tree. I'll send the new
patches as a reply to this mail.
git://git.kernel.org/pub/scm/linux/kernel/git/willy/misc.git semaphore-20080314
Changes:
- Dropped all the asm/semaphore.h changes. They're just causing
conflicts for linux-next, and while Stephen assures me that fixing
them up is trivial and he doesn't mind, I'd rather not burn him out
prematurely. I still intend to push them, but they don't need to be
part of linux-next, IMO.
- Split the addition of down_killable() out of the main patch. It's
logically separate (adding a new interface), and it was sheer
laziness to not split it out in the first place.
- New functionality! down_timeout(). Just look at the mess in
acpi/osl.c where it tries to emulate it. It's very little extra code
to add it to kernel/semaphore.c, so I thought it was a good idea.
- Simplify the implementation. Dave Howells said the current algorithm
makes his head hurt, and in retrospect, perhaps I was just trying to
be too clever.
- Fix the lockdep bug (thanks to Peter Zijlstra)
- Remove an unsightly and unnecessary unlikely() (thanks to Harvey Harrison)
- Fix the down() while interrupts disabled bug (thanks to Ingo Molnar)
(I may have posted this one before. Not sure.)
I've tested the end result of this with Dave Howells' synchro-test module
and not found any problems.
If you prefer, you can also find the patches at
http://git.kernel.org/?p=linux/kernel/git/willy/misc.git;a=shortlog;h=semaphore-20080314
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next reply other threads:[~2008-03-14 20:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-14 20:42 Matthew Wilcox [this message]
2008-03-14 20:44 ` [PATCH 1/6] Fix quota.h includes Matthew Wilcox
2008-03-14 20:44 ` [PATCH 2/6] Add semaphore.h to kernel_lock.c Matthew Wilcox
2008-03-14 20:44 ` [PATCH 3/6] Generic semaphore implementation Matthew Wilcox
2008-03-14 20:44 ` [PATCH 4/6] Introduce down_killable() Matthew Wilcox
2008-03-14 20:44 ` [PATCH 5/6] Add down_timeout and change ACPI to use it Matthew Wilcox
2008-03-14 20:44 ` [PATCH 6/6] Simplify semaphore implementation Matthew Wilcox
2008-03-14 20:59 ` Updated generic semaphore patch set Harvey Harrison
2008-03-14 21:23 ` Harvey Harrison
2008-03-14 23:37 ` Johannes Weiner
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=20080314204248.GV613@parisc-linux.org \
--to=matthew@wil.cx \
--cc=dhowells@redhat.com \
--cc=harvey.harrison@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
/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