From: "David S. Miller" <davem@davemloft.net>
To: James.Bottomley@steeleye.com
Cc: linux-arch@vger.kernel.org
Subject: Re: Potential problem with the page_mapping macro and flush_dcache_page()
Date: Sun, 19 Mar 2006 13:25:11 -0800 (PST) [thread overview]
Message-ID: <20060319.132511.116548328.davem@davemloft.net> (raw)
In-Reply-To: <1142802286.3240.54.camel@mulgrave.il.steeleye.com>
From: James Bottomley <James.Bottomley@SteelEye.com>
Date: Sun, 19 Mar 2006 15:04:46 -0600
> On Sun, 2006-03-19 at 13:00 -0800, David S. Miller wrote:
> > You have physically indexed caches, thus cache coherency transactions
> > should purge all cache lines with that same physical TAG.
>
> No, we have virtually indexed but physically tagged caches; this is why
> we have the problem (we have to select one of the aliases to flush).
This is exactly what Sparc64's caches are too, L1 D-cache is virtually
indexed and physically tagged. But any bus coherency transaction will
update all lines with matching physical tags, otherwise things just
won't work.
> > Direct I/O is another problematic case.
>
> OK, I confess to not ever having looked at that ... does it use
> get_user_pages() as well?
I believe so, Andrew knows...
next prev parent reply other threads:[~2006-03-19 21:25 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 [this message]
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
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=20060319.132511.116548328.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=James.Bottomley@steeleye.com \
--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