From: Andrew Morton <akpm@osdl.org>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: davem@davemloft.net, linux-arch@vger.kernel.org
Subject: Re: Potential problem with the page_mapping macro and flush_dcache_page()
Date: Wed, 22 Mar 2006 22:20:27 -0800 [thread overview]
Message-ID: <20060322222027.4615e245.akpm@osdl.org> (raw)
In-Reply-To: <1142803783.3240.64.camel@mulgrave.il.steeleye.com>
James Bottomley <James.Bottomley@SteelEye.com> wrote:
>
> > > OK, I confess to not ever having looked at that ... does it use
> > > get_user_pages() as well?
> >
> > I believe so, Andrew knows...
>
> OK I'll wait to see what he says.
<he'd made some procmailrc changes and had thought that linux-arch was
rather quiet lately>
Yes, direct-io does get_user_pages() and then uses submit_bio() to
read/write the pages.
So it should fall under
2) device DMA, where the L2 cache eviction done by the device DMA
will pull out the D-cache entries, or if the block I/O is via PIO
it will do cache flushing in there, as per some asm-*/ide.h
implementations of __ide_ins*()/__ide_outs*()
umm, except in the case where direct-io hit a file hole. In that case we
memset the user's page and use flush_dcache_page(). And that's most likely
an anonymous page.
next prev parent reply other threads:[~2006-03-23 6:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-19 17:15 Potential problem with the page_mapping macro and flush_dcache_page() James Bottomley
2006-03-19 20:33 ` David S. Miller
2006-03-19 20:53 ` James Bottomley
2006-03-19 21:00 ` David S. Miller
2006-03-19 21:04 ` James Bottomley
2006-03-19 21:23 ` James Bottomley
2006-03-19 21:26 ` David S. Miller
2006-03-19 23:50 ` James Bottomley
2006-03-20 1:15 ` James Bottomley
2006-03-19 21:25 ` David S. Miller
2006-03-19 21:29 ` James Bottomley
2006-03-19 22:01 ` David S. Miller
2006-03-19 23:39 ` James Bottomley
2006-03-19 23:42 ` David S. Miller
2006-03-23 6:20 ` Andrew Morton [this message]
2006-03-23 14:13 ` James Bottomley
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=20060322222027.4615e245.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=James.Bottomley@steeleye.com \
--cc=davem@davemloft.net \
--cc=linux-arch@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