From: Nick Piggin <nickpiggin@yahoo.com.au>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: "David S. Miller" <davem@davemloft.net>,
anton@samba.org, linux-arch@vger.kernel.org,
Andrew Morton <akpm@osdl.org>, Peter Keilty <Peter.Keilty@hp.com>
Subject: Re: Global spinlock vs local bit spin locks
Date: Fri, 17 Jun 2005 19:21:57 +1000 [thread overview]
Message-ID: <42B29635.2020700@yahoo.com.au> (raw)
In-Reply-To: <20050617084521.GG3913@holomorphy.com>
William Lee Irwin III wrote:
>
> I'm ambivalent now I guess. I'm not wild about bh's in the first place,
> so infecting core code with new dependencies on them doesn't sound hot,
> though I still can't help cringing at using a bitflag in the first bh
> in the list to protect against concurrent teardown of the bh list,
> which relies on the setup/teardown patterns.
>
It's not quite as bad as that - there will be no teardown while
any of the buffers are still in flight. The lock is simply to
protect concurrent completion of requests, it could just as
easily go in the last bh.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
next prev parent reply other threads:[~2005-06-17 9:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-17 4:21 Global spinlock vs local bit spin locks Nick Piggin
2005-06-17 4:45 ` Andrew Morton
2005-06-17 8:50 ` Andi Kleen
2005-06-17 4:45 ` David S. Miller
2005-06-17 4:46 ` William Lee Irwin III
2005-06-17 4:52 ` Andrew Morton
2005-06-17 8:35 ` Nick Piggin
2005-06-17 8:45 ` William Lee Irwin III
2005-06-17 9:21 ` Nick Piggin [this message]
2005-06-17 9:28 ` William Lee Irwin III
2005-06-17 8:54 ` Andi Kleen
2005-06-17 9:15 ` William Lee Irwin III
2005-06-17 9:27 ` Nick Piggin
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=42B29635.2020700@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=Peter.Keilty@hp.com \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=davem@davemloft.net \
--cc=linux-arch@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox