From: David Howells <dhowells@redhat.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: dhowells@redhat.com, Nick Piggin <npiggin@suse.de>,
linux-arch@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [rfc] io memory barriers, and getting rid of mmiowb
Date: Tue, 20 Nov 2007 17:04:46 +0000 [thread overview]
Message-ID: <4873.1195578286@redhat.com> (raw)
In-Reply-To: <20071120165812.GH12494@parisc-linux.org>
Matthew Wilcox <matthew@wil.cx> wrote:
> > Should there be a spin_lock_io() for example?
>
> Then we need ...
Yeah.
David
next prev parent reply other threads:[~2007-11-20 17:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 16:02 [rfc] io memory barriers, and getting rid of mmiowb Nick Piggin
2007-11-20 16:46 ` David Howells
2007-11-20 16:58 ` Matthew Wilcox
2007-11-20 17:04 ` David Howells [this message]
2007-11-21 0:30 ` Nick Piggin
2007-11-21 1:53 ` David Howells
2007-11-22 8:23 ` Nick Piggin
2007-11-21 13:50 ` Ralf Baechle
2007-11-22 8:04 ` 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=4873.1195578286@redhat.com \
--to=dhowells@redhat.com \
--cc=benh@kernel.crashing.org \
--cc=linux-arch@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=npiggin@suse.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).