From: Matthew Wilcox <matthew@wil.cx>
To: Nick Piggin <npiggin@suse.de>
Cc: MinChan Kim <minchan.kim@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, akpm@linux-foundation.org,
linux-parisc@vger.kernel.org
Subject: Re: [PATCH] Remove needless flush_dcache_page call
Date: Thu, 15 Jan 2009 23:01:24 -0700 [thread overview]
Message-ID: <20090116060124.GG31013@parisc-linux.org> (raw)
In-Reply-To: <20090116055927.GA22810@wotan.suse.de>
On Fri, Jan 16, 2009 at 06:59:27AM +0100, Nick Piggin wrote:
> But there are quite possibly holes around here because not as much testing
> is done on CPUs with these kinds of caches. Eg. brd probably should be
> doing a flush_dcache_page in the rw == WRITE direction AFAIKS, so it picks
> up user aliases here.
Nick, if you wanted me to schlep a parisc machine to LCA for you, you
needed to ask me *before* I got as far as Vancouver ;-)
--
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."
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Wilcox <matthew@wil.cx>
To: Nick Piggin <npiggin@suse.de>
Cc: MinChan Kim <minchan.kim@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, akpm@linux-foundation.org,
linux-parisc@vger.kernel.org
Subject: Re: [PATCH] Remove needless flush_dcache_page call
Date: Thu, 15 Jan 2009 23:01:24 -0700 [thread overview]
Message-ID: <20090116060124.GG31013@parisc-linux.org> (raw)
In-Reply-To: <20090116055927.GA22810@wotan.suse.de>
On Fri, Jan 16, 2009 at 06:59:27AM +0100, Nick Piggin wrote:
> But there are quite possibly holes around here because not as much testing
> is done on CPUs with these kinds of caches. Eg. brd probably should be
> doing a flush_dcache_page in the rw == WRITE direction AFAIKS, so it picks
> up user aliases here.
Nick, if you wanted me to schlep a parisc machine to LCA for you, you
needed to ask me *before* I got as far as Vancouver ;-)
--
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."
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-01-16 6:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 5:28 [PATCH] Remove needless flush_dcache_page call MinChan Kim
2009-01-16 5:28 ` MinChan Kim
2009-01-16 5:33 ` Matthew Wilcox
2009-01-16 5:33 ` Matthew Wilcox
2009-01-16 5:51 ` MinChan Kim
2009-01-16 5:51 ` MinChan Kim
2009-01-16 5:57 ` Matthew Wilcox
2009-01-16 5:57 ` Matthew Wilcox
2009-01-16 6:08 ` MinChan Kim
2009-01-16 6:08 ` MinChan Kim
2009-01-16 6:13 ` Nick Piggin
2009-01-16 6:13 ` Nick Piggin
2009-01-16 6:16 ` MinChan Kim
2009-01-16 6:16 ` MinChan Kim
2009-01-16 5:59 ` Nick Piggin
2009-01-16 5:59 ` Nick Piggin
2009-01-16 6:01 ` Matthew Wilcox [this message]
2009-01-16 6:01 ` Matthew Wilcox
2009-01-16 7:34 ` Nick Piggin
2009-01-16 14:28 ` James Bottomley
2009-01-16 16:28 ` Kyle McMartin
2009-01-16 17:34 ` Grant Grundler
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=20090116060124.GG31013@parisc-linux.org \
--to=matthew@wil.cx \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-parisc@vger.kernel.org \
--cc=minchan.kim@gmail.com \
--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 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.