From: James Bottomley <James.Bottomley@SteelEye.com>
To: Russell King <rmk+lkml@arm.linux.org.uk>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: fuse, get_user_pages, flush_anon_page, aliasing caches and all that again
Date: Mon, 01 Jan 2007 10:04:22 -0500 [thread overview]
Message-ID: <1167663862.5302.54.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <20061221165744.GD3958@flint.arm.linux.org.uk>
On Thu, 2006-12-21 at 16:57 +0000, Russell King wrote:
> I'm not entirely convinced that it can be replaced. What if the page
> is in the page cache and is shared with other processes? That quite
> clearly falls under flush_dcache_page()'s remit.
Actually, it should work. flush_dcache_page() is the big hammer, it
clears the caches of all the user processes and the kernel for that
page. On most architectures this is not that expensive, but on parisc
it is. Most of the paths out of fuse have already called
flush_dcache_page() coming in to make the page coherent for the kernel
to use. Then fuse writes data to the page. There's no point calling it
again since there shouldn't be anything in the user cache (the model has
the kernel owning the page), so flush_kernel_dcache_page() is the
shortcut to simply flush out the kernel cache above the page (knowing
the users still have the page uncached).
James
next prev parent reply other threads:[~2007-01-01 15:04 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-21 15:26 Russell King
2006-12-21 15:53 ` Miklos Szeredi
2006-12-21 16:57 ` Russell King
2006-12-21 17:51 ` Miklos Szeredi
2006-12-21 21:04 ` Jan Engelhardt
2006-12-21 21:30 ` Miklos Szeredi
2007-01-01 15:04 ` James Bottomley [this message]
2006-12-21 17:17 ` Russell King
2006-12-21 17:55 ` Miklos Szeredi
2006-12-21 18:11 ` Russell King
2006-12-21 18:30 ` Miklos Szeredi
2006-12-21 18:55 ` Russell King
2006-12-21 19:05 ` Miklos Szeredi
2006-12-21 23:51 ` Randolph Chung
2006-12-22 8:43 ` Russell King
2006-12-22 14:45 ` Randolph Chung
2006-12-30 16:39 ` Russell King
2006-12-30 16:50 ` Russell King
2006-12-30 18:26 ` Linus Torvalds
2006-12-30 22:46 ` Russell King
2006-12-31 5:23 ` David Miller
2006-12-31 9:10 ` Miklos Szeredi
2006-12-31 9:45 ` David Miller
2006-12-31 9:23 ` Russell King
2006-12-31 9:27 ` Arjan van de Ven
2006-12-31 9:47 ` David Miller
2006-12-31 10:00 ` Russell King
2006-12-31 10:04 ` David Miller
2006-12-31 12:24 ` Miklos Szeredi
2006-12-31 17:37 ` Russell King
2007-01-01 22:15 ` Miklos Szeredi
2007-01-01 23:45 ` Russell King
2007-01-02 19:40 ` Dan Williams
2007-01-02 22:53 ` James Bottomley
2007-01-02 23:19 ` David Miller
2007-01-02 23:34 ` James Bottomley
2007-01-03 0:20 ` David Miller
2007-01-03 14:16 ` Russell King
2007-01-03 15:00 ` James Bottomley
2007-01-03 15:09 ` Russell King
2007-01-07 16:09 ` James Bottomley
2007-01-07 16:30 ` Russell King
2006-12-31 20:40 ` David Miller
2006-12-31 20:58 ` Linus Torvalds
2006-12-31 21:12 ` David Miller
2007-01-01 16:44 ` James Bottomley
2007-01-01 23:04 ` David Miller
2007-01-01 23:23 ` James Bottomley
[not found] ` <1167669252.5302.57.camel@mulgrave.il.steeleye.com>
2007-01-01 23:01 ` David Miller
2007-01-01 23:17 ` Russell King
2006-12-31 9:55 ` Russell King
2006-12-31 9:46 ` David Miller
2007-01-01 14:35 ` James Bottomley
2007-01-01 16:21 ` Russell King
2006-12-30 18:21 ` Linus Torvalds
2006-12-21 16:29 ` Arjan van de Ven
2006-12-21 17:35 ` Russell King
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=1167663862.5302.54.camel@mulgrave.il.steeleye.com \
--to=james.bottomley@steeleye.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=rmk+lkml@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®