From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Lameter <clameter@sgi.com>,
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 15:51:13 +1000 [thread overview]
Message-ID: <464A9BD1.1030300@yahoo.com.au> (raw)
In-Reply-To: <20070515222912.ae836e00.akpm@linux-foundation.org>
Andrew Morton wrote:
> On Wed, 16 May 2007 14:52:05 +1000 Nick Piggin <nickpiggin@yahoo.com.au> wrote:
>>>On the other hand non highmem platforms are burdened with always repeating
>>>the same KM_USER0 in every function call. Isnt it enough to know that
>>>standard functions use KM_USER0 for their operations?
>>
>>Couldn't that be filtered out inline?
>
>
> It is - there is no runtime overhead for non-highmem machines.
>
> The problem nowadays is all the developers who don't need, have, compile
> for or test on highmem machines.
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 :)
--
SUSE Labs, Novell Inc.
next prev parent reply other threads:[~2007-05-16 5:51 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 [this message]
2007-05-16 6:13 ` Christoph Lameter
2007-05-16 6:19 ` Nick Piggin
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=464A9BD1.1030300@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox