From: Jamie Lokier <jamie@shareable.org>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: anfei <anfei.zhou@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux@arm.linux.org.uk
Subject: Re: cache alias in mmap + write
Date: Thu, 21 Jan 2010 01:32:05 +0000 [thread overview]
Message-ID: <20100121013205.GA29808@shareable.org> (raw)
In-Reply-To: <20100121094733.3778.A69D9226@jp.fujitsu.com>
KOSAKI Motohiro wrote:
> 2. Add some commnet. almost developer only have x86 machine. so, arm
> specific trick need additional explicit explanation. otherwise anybody
> might break this code in the future.
That's Documentation/cachetlb.txt.
What's being discussed here is not ARM-specific, although it appears
maintainers of different architecture (ARM and MIPS for a start) may
have different ideas about what they are guaranteeing to userspace.
It sounds like MIPS expects userspace to use msync() sometimes (even
though Linux msync(MS_INVALIDATE) is quite broken), and ARM expects to
to keep mappings coherent automatically (which is sometimes slower
than necessary, but usually very helpful).
> 3. Resend the patch. original mail isn't good patch format. please
> consider to reduce akpm suffer.
This type of change in generic code would need review from a number of
architecture maintainers, I'd expect.
-- Jamie
--
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:[~2010-01-21 1:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 8:26 cache alias in mmap + write anfei
2010-01-20 9:10 ` KOSAKI Motohiro
2010-01-20 9:52 ` anfei
2010-01-21 1:10 ` KOSAKI Motohiro
2010-01-21 1:32 ` Jamie Lokier [this message]
2010-01-21 3:06 ` anfei zhou
2010-01-21 2:39 ` anfei zhou
2010-01-21 4:59 ` anfei zhou
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=20100121013205.GA29808@shareable.org \
--to=jamie@shareable.org \
--cc=anfei.zhou@gmail.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@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;
as well as URLs for NNTP newsgroup(s).