From: Linus Torvalds <torvalds@linux-foundation.org>
To: Nick Piggin <npiggin@suse.de>
Cc: linux-ia64@vger.kernel.org, Jesse Barnes <jesse.barnes@intel.com>,
linuxppc-dev@ozlabs.org
Subject: Re: wmb vs mmiowb
Date: Thu, 23 Aug 2007 16:14:42 +0000 [thread overview]
Message-ID: <alpine.LFD.0.999.0708230913470.30176@woody.linux-foundation.org> (raw)
In-Reply-To: <20070823035448.GG18788@wotan.suse.de>
On Thu, 23 Aug 2007, Nick Piggin wrote:
>
> OK, but we'd have some kind of functions that are called not to
> serialise the CPUs, but to serialise the IO. It would be up to
> the calling code to already provide CPU synchronisation.
>
> serialize_io(); / unserialize_io(); / a nicer name
We could call it "mmiowb()", for example?
Radical idea, I know.
> If we could pass in some kind of relevant resoure (eg. the IO
> memory or device or something), then we might even be able to
> put debug checks there to ensure two CPUs are never inside the
> same critical IO section at once.
We could certainly give it the spinlock as an argument.
Linus
next prev parent reply other threads:[~2007-08-23 16:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-22 4:57 wmb vs mmiowb Nick Piggin
2007-08-22 18:07 ` Linus Torvalds
2007-08-22 19:02 ` Jesse Barnes
2007-08-23 2:20 ` Nick Piggin
2007-08-23 2:57 ` Linus Torvalds
2007-08-23 3:54 ` Nick Piggin
2007-08-23 16:14 ` Linus Torvalds [this message]
2007-08-23 4:20 ` Nick Piggin
2007-08-23 16:16 ` Linus Torvalds
2007-08-23 16:27 ` Benjamin Herrenschmidt
2007-08-24 3:09 ` Nick Piggin
2007-08-28 20:56 ` Brent Casavant
2007-08-29 0:59 ` Nick Piggin
2007-08-29 18:53 ` Brent Casavant
2007-08-30 3:36 ` Nick Piggin
2007-08-30 19:42 ` Brent Casavant
2007-09-03 20:48 ` Nick Piggin
2007-08-24 2:59 ` Nick Piggin
2007-08-23 17:02 ` Jesse Barnes
2007-08-23 1:59 ` Nick Piggin
2007-08-23 7:27 ` Benjamin Herrenschmidt
2007-08-23 16:56 ` Jesse Barnes
2007-08-24 3:12 ` Nick Piggin
2007-08-28 21:21 ` Brent Casavant
2007-08-28 23:01 ` Peter Chubb
2007-08-23 7:25 ` Benjamin Herrenschmidt
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=alpine.LFD.0.999.0708230913470.30176@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=jesse.barnes@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=npiggin@suse.de \
/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