From: Matthew Wilcox <matthew@wil.cx>
To: Matt Fleming <matt@console-pimps.org>
Cc: James Bottomley <James.Bottomley@suse.de>,
linux-arch@vger.kernel.org, linux-parisc@vger.kernel.org,
Christoph Hellwig <hch@lst.de>,
Russell King <rmk@arm.linux.org.uk>,
Paul Mundt <lethal@linux-sh.org>
Subject: Re: [PATCHv2 1/5] mm: add coherence API for DMA to vmalloc/vmap areas
Date: Thu, 24 Dec 2009 05:39:13 -0700 [thread overview]
Message-ID: <20091224123913.GD5335@parisc-linux.org> (raw)
In-Reply-To: <20091224100853.GA3165@console-pimps.org>
On Thu, Dec 24, 2009 at 10:08:53AM +0000, Matt Fleming wrote:
> On Wed, Dec 23, 2009 at 03:22:21PM -0600, James Bottomley wrote:
> > +
> > + void flush_kernel_vmap_range(void *vaddr, int size)
> > + flushes the kernel cache for a given virtual address range in
> > + the vmap area. This API makes sure that and data the kernel
>
> ^^^ code and data?
I'd guess it's a typo for 'any data'.
> > + void invalidate_kernel_vmap_range(void *vaddr, int size)
> > + invalidates the kernel cache for a given virtual address range
> > + in the vmap area. This API is designed to make sure that while
> > + I/O went on to an address range in the vmap area, the processor
> > + didn't speculate cache reads and thus make the cache over the
> > + virtual address stale.
> > +
>
> Could this sentence be reworked a little? I find the "over the virtual
> address" part a little difficult to parse.
How about:
invalidates the processor cache for a given virtual address range
in the vmap area. This API addresses the problem that the processor
may have performed speculative reads into its cache of the vmapped
area while I/O was occurring to the underlying physical pages.
Signed-off-by: Matthew Wilcox <willy@linux.intel.com>
--
Matthew Wilcox Intel Open Source Technology Centre
"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:[~2009-12-24 12:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-23 21:22 [PATCHv2 0/5] fix xfs by making I/O to vmap/vmalloc areas work James Bottomley
2009-12-23 21:22 ` [PATCHv2 1/5] mm: add coherence API for DMA to vmalloc/vmap areas James Bottomley
2009-12-23 21:22 ` [PATCHv2 2/5] parisc: add mm " James Bottomley
2009-12-23 21:22 ` [PATCHv2 3/5] arm: " James Bottomley
2009-12-23 21:22 ` [PATCHv2 4/5] sh: " James Bottomley
2009-12-23 21:22 ` [PATCHv2 5/5] xfs: fix xfs to work with Virtually Indexed architectures James Bottomley
2009-12-24 11:03 ` Christoph Hellwig
2009-12-27 15:32 ` James Bottomley
2010-01-02 21:33 ` [PATCHv2 2/5] parisc: add mm API for DMA to vmalloc/vmap areas Benjamin Herrenschmidt
2010-01-02 21:53 ` James Bottomley
2010-01-03 20:12 ` Benjamin Herrenschmidt
2009-12-24 10:08 ` [PATCHv2 1/5] mm: add coherence " Matt Fleming
2009-12-24 12:39 ` Matthew Wilcox [this message]
2009-12-24 13:06 ` Matt Fleming
2009-12-27 15:37 ` James Bottomley
2010-01-02 21:27 ` Benjamin Herrenschmidt
2010-01-02 21:54 ` James Bottomley
2010-01-03 20:14 ` 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=20091224123913.GD5335@parisc-linux.org \
--to=matthew@wil.cx \
--cc=James.Bottomley@suse.de \
--cc=hch@lst.de \
--cc=lethal@linux-sh.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=rmk@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.