From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Christoph Lameter <clameter@sgi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Satyam Sharma <satyam.sharma@gmail.com>,
Nate Diller <nate.diller@gmail.com>
Subject: Re: Pagecache zeroing: zero_user_segment, zero_user_segments and zero_user
Date: Wed, 16 May 2007 16:19:49 +1000 [thread overview]
Message-ID: <464AA285.4010309@yahoo.com.au> (raw)
In-Reply-To: <Pine.LNX.4.64.0705152309180.5772@schroedinger.engr.sgi.com>
Christoph Lameter wrote:
> On Wed, 16 May 2007, Nick Piggin wrote:
>
>
>>Well sure, if that's all Christoph is worried about, then it isn't
>>really valid because in generic code we have to follow the architecture
>>abstraction API -- there is no "non highmem platform" in generic code :)
>
>
> But there is a default KM_USER0 that is used in many functions.
>
> F.e.
>
> filemap_copy_from_user *_iovec xip_truncate_page clear_user_highpage
> clear_highpage copy_user_highpage copy_highpage
>
> So explicitly mentioning KM_USER0 in every function call is not a
> requirement.
You probably have an argument there... but that's not to do with
highmem platforms or not.
--
SUSE Labs, Novell Inc.
next prev parent reply other threads:[~2007-05-16 6:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 3:00 Pagecache zeroing: zero_user_segment, zero_user_segments and zero_user Christoph Lameter
2007-05-16 3:24 ` Andrew Morton
2007-05-16 4:05 ` Christoph Lameter
2007-05-16 4:52 ` Nick Piggin
2007-05-16 5:29 ` Andrew Morton
2007-05-16 5:51 ` Nick Piggin
2007-05-16 6:13 ` Christoph Lameter
2007-05-16 6:19 ` Nick Piggin [this message]
2007-05-16 17:39 ` Satyam Sharma
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=464AA285.4010309@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nate.diller@gmail.com \
--cc=satyam.sharma@gmail.com \
/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.