From: Matthew Wilcox <matthew@wil.cx>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Andi Kleen <ak@linux.intel.com>,
Zhao Yakui <yakui.zhao@intel.com>,
Daniel Walker <dwalker@mvista.com>,
linux-acpi@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
len.brown@intel.com,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 1/3] acpi: add real mutex function calls
Date: Mon, 21 Jul 2008 13:55:45 -0600 [thread overview]
Message-ID: <20080721195545.GI24246@parisc-linux.org> (raw)
In-Reply-To: <1216668835.7257.91.camel@twins>
On Mon, Jul 21, 2008 at 09:33:55PM +0200, Peter Zijlstra wrote:
> Does ACPICA use counting semaphores? If so, you could have used real
> arguments against his patches, instead of this other-os bull.
Yep. In theory, it allows for a more powerful implementation than
Linux's semaphores (allowing you to do the equivalent of init_sem(5);
down(1); down(3); down(2); and have the third down() block until there's
two units available). In practice, no ACPI code is asking for more than
one unit at a time.
> Also, what is the justification for using counting semaphores? Are we
> counting hardware slots or is it just generic ACPI braindamage?
It's the interface that AML is allowed to use, iirc. So short of
revising the spec ... we have no idea how hardware are using it.
> Clearly this all wasn't extremely clear from the code - otherwise Daniel
> wouldn't even have done these patches.
Some people get religion about a topic and push pointless patches
anyway.
> > Especially now that semaphores are not duplicated per architecture
> > anymore so actually keeping them around is not that costly.
>
> Having them around might give people the idea its a good idea to use
> them. Not having them around is a good way to discourage that.
We'll end up making completions be more of a mess than semaphores ever
were or pushing semaphore implementations into every user that really
wanted a counting semaphore implementation. People need to drop this
crusade, it's causing more harm than good.
--
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 prev parent reply other threads:[~2008-07-21 19:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 18:16 [PATCH 0/3] acpi: acpi: sem out, mutex/completion in Daniel Walker
2008-07-19 18:16 ` [PATCH 1/3] acpi: add real mutex function calls Daniel Walker
2008-07-19 18:16 ` [PATCH 2/3] acpi: semaphore removal Daniel Walker
2008-07-19 18:16 ` [PATCH 3/3] Add lockdep integration for the ACPI mutex usage Daniel Walker
2008-07-20 8:15 ` [PATCH 2/3] acpi: semaphore removal Dave Chinner
2008-07-20 14:49 ` Daniel Walker
2008-07-21 1:51 ` [PATCH 1/3] acpi: add real mutex function calls Zhao Yakui
2008-07-21 9:14 ` Peter Zijlstra
2008-07-21 9:17 ` Andi Kleen
2008-07-21 9:24 ` Peter Zijlstra
2008-07-21 19:15 ` Andi Kleen
2008-07-21 19:33 ` Peter Zijlstra
2008-07-21 19:55 ` Matthew Wilcox [this message]
2008-07-21 20:22 ` Daniel Walker
2008-07-21 20:00 ` Andi Kleen
2008-07-21 20:38 ` Daniel Walker
2008-07-21 13:59 ` Daniel Walker
2008-07-21 13:56 ` Daniel Walker
2008-07-21 19:20 ` Andi Kleen
2008-07-21 19:39 ` Daniel Walker
2008-07-23 22:14 ` Moore, Robert
2008-07-24 12:44 ` Daniel Walker
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=20080721195545.GI24246@parisc-linux.org \
--to=matthew@wil.cx \
--cc=ak@linux.intel.com \
--cc=dwalker@mvista.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
--cc=yakui.zhao@intel.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