From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: unlock_buffer() and clear_bit()
Date: Fri, 24 Mar 2006 21:46:09 +0000 [thread overview]
Message-ID: <200603242145.k2OLjog18835@unix-os.sc.intel.com> (raw)
In-Reply-To: <44240DB3.3040502@bull.net>
Zoltan Menyhart wrote on Friday, March 24, 2006 7:18 AM
> I wonder if "unlock_buffer()" works correctly on ia64...
>
> As far As I can see, nothing makes it sure that data modifications
> issued inside the critical section be globally visible before the
> "BH_Lock" bit gets cleared.
Are you saying the memory ordering in unlock_buffer() is x86 centric
that relies on arch specific write ordering? (on x86, write to memory
implies a release semantics w.r.t. read proceed it). It's better to
bring this up on LKML. If your concern is true, then it is a bug in
the generic code that lacks smp_mb__before_clear_bit.
- Ken
prev parent reply other threads:[~2006-03-24 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 15:18 unlock_buffer() and clear_bit() Zoltan Menyhart
2006-03-24 21:46 ` Chen, Kenneth W [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=200603242145.k2OLjog18835@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.com \
--cc=linux-ia64@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