From: Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com>
To: davidm@hpl.hp.com
Cc: akepner@sgi.com, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org, akpm@osdl.org, jbarnes@sgi.com
Subject: Re: bug in 2.6.9-rc4-mm1 ia64/mm/init.c
Date: Wed, 13 Oct 2004 08:56:48 +0000 [thread overview]
Message-ID: <416CEF0E.1060406@jp.fujitsu.com> (raw)
In-Reply-To: <16748.60002.875945.950324@napali.hpl.hp.com>
David Mosberger wrote:
>>>>>>On Wed, 13 Oct 2004 17:44:10 +0900, Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com> said:
>
>
> Hiroyuki> My purpose was to reduce # of page fault when
> Hiroyuki> ia64_pfn_valid() is called. It is called heavily in
> Hiroyuki> bad_range() (in mm/page_alloc.c) now.
>
> At the expense of ignoring perfectly good memory? Or did I miss something?
>
> --david
Am I ignoring some good memory ?
I think GRANULEROUNDDOWN(start)/GRANULEROUNDUP(end) only expand valid pfn range,
do I misunderstanding something ?
-- Kame
WARNING: multiple messages have this Message-ID (diff)
From: Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com>
To: davidm@hpl.hp.com
Cc: akepner@sgi.com, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org, akpm@osdl.org, jbarnes@sgi.com
Subject: Re: bug in 2.6.9-rc4-mm1 ia64/mm/init.c
Date: Wed, 13 Oct 2004 18:02:06 +0900 [thread overview]
Message-ID: <416CEF0E.1060406@jp.fujitsu.com> (raw)
In-Reply-To: <16748.60002.875945.950324@napali.hpl.hp.com>
David Mosberger wrote:
>>>>>>On Wed, 13 Oct 2004 17:44:10 +0900, Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com> said:
>
>
> Hiroyuki> My purpose was to reduce # of page fault when
> Hiroyuki> ia64_pfn_valid() is called. It is called heavily in
> Hiroyuki> bad_range() (in mm/page_alloc.c) now.
>
> At the expense of ignoring perfectly good memory? Or did I miss something?
>
> --david
Am I ignoring some good memory ?
I think GRANULEROUNDDOWN(start)/GRANULEROUNDUP(end) only expand valid pfn range,
do I misunderstanding something ?
-- Kame
next prev parent reply other threads:[~2004-10-13 8:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 0:21 bug in 2.6.9-rc4-mm1 ia64/mm/init.c akepner
2004-10-13 0:21 ` akepner
2004-10-13 1:24 ` Hiroyuki KAMEZAWA
2004-10-13 1:24 ` Hiroyuki KAMEZAWA
2004-10-13 1:46 ` Hiroyuki KAMEZAWA
2004-10-13 1:46 ` Hiroyuki KAMEZAWA
2004-10-13 8:04 ` David Mosberger
2004-10-13 8:04 ` David Mosberger
2004-10-13 8:44 ` Hiroyuki KAMEZAWA
2004-10-13 8:44 ` Hiroyuki KAMEZAWA
2004-10-13 8:42 ` David Mosberger
2004-10-13 8:42 ` David Mosberger
2004-10-13 8:56 ` Hiroyuki KAMEZAWA [this message]
2004-10-13 9:02 ` Hiroyuki KAMEZAWA
2004-10-14 4:49 ` Hiroyuki KAMEZAWA
2004-10-14 4:49 ` Hiroyuki KAMEZAWA
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=416CEF0E.1060406@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akepner@sgi.com \
--cc=akpm@osdl.org \
--cc=davidm@hpl.hp.com \
--cc=jbarnes@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@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 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.