linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hiroyuki KAMEZAWA <kamezawa.hiroyu@jp.fujitsu.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
	LinuxIA64 <linux-ia64@vger.kernel.org>,
	linux-mm <linux-mm@kvack.org>
Subject: Re: [RFC/PATCH]  pfn_valid() more generic : arch independent part[0/2]
Date: Fri, 08 Oct 2004 08:38:24 +0900	[thread overview]
Message-ID: <4165D370.1090208@jp.fujitsu.com> (raw)
In-Reply-To: <1248570000.1097159887@[10.10.2.4]>

Martin J. Bligh wrote:
> The normal way to fix the above is just to have a bitmap array to test - 
> in your case a 1GB granularity would be sufficicent. That takes < 1 word
> to implement for the example above ;-)
> 
> M.
> 

Although I don't like a page fault, I now understand it doesn't often happen.
I'd like to use current implementation.

Thanks

Kame <kamezawa.hiroyu@jp.fujitsu.com>
--
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:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2004-10-07 23:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-07  5:22 Luck, Tony
2004-10-07  6:28 ` Hiroyuki KAMEZAWA
2004-10-07  6:51   ` align vmemmap to ia64's granule Hiroyuki KAMEZAWA
2004-10-07 14:38   ` [RFC/PATCH] pfn_valid() more generic : arch independent part[0/2] Martin J. Bligh
2004-10-07 23:38     ` Hiroyuki KAMEZAWA [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-10-07 15:53 Luck, Tony
2004-10-07 16:02 ` Martin J. Bligh
2004-10-06  6:37 Hiroyuki KAMEZAWA
2004-10-06 15:14 ` Martin J. Bligh
2004-10-07  0:10   ` 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=4165D370.1090208@jp.fujitsu.com \
    --to=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mbligh@aracnet.com \
    --cc=tony.luck@intel.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