From: David Rientjes <rientjes@google.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-mm@kvack.org, mel@csn.ul.ie, y-goto@jp.fujitsu.com,
clameter@sgi.com, hugh@veritas.com
Subject: Re: [RFC] memory unplug v5 [3/6] walk memory resources assist function.
Date: Thu, 14 Jun 2007 23:05:22 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.0.99.0706142304530.1729@chino.kir.corp.google.com> (raw)
In-Reply-To: <20070614160156.9aa218ec.kamezawa.hiroyu@jp.fujitsu.com>
On Thu, 14 Jun 2007, KAMEZAWA Hiroyuki wrote:
> Index: devel-2.6.22-rc4-mm2/kernel/resource.c
> ===================================================================
> --- devel-2.6.22-rc4-mm2.orig/kernel/resource.c
> +++ devel-2.6.22-rc4-mm2/kernel/resource.c
> @@ -244,7 +244,7 @@ EXPORT_SYMBOL(release_resource);
> * the caller must specify res->start, res->end, res->flags.
> * If found, returns 0, res is overwritten, if not found, returns -1.
> */
> -int find_next_system_ram(struct resource *res)
> +static int find_next_system_ram(struct resource *res)
> {
> resource_size_t start, end;
> struct resource *p;
> @@ -277,6 +277,30 @@ int find_next_system_ram(struct resource
> res->end = p->end;
> return 0;
> }
> +
> +int walk_memory_resource(unsigned long start_pfn, unsigned long nr_pages,
> + void *arg, walk_memory_callback_t func)
> +{
> + struct resource res;
> + unsigned long pfn, len;
> + u64 orig_end;
> + int ret;
> + res.start = (u64) start_pfn << PAGE_SHIFT;
> + res.end = ((u64)(start_pfn + nr_pages) << PAGE_SHIFT) - 1;
> + res.flags = IORESOURCE_MEM;
> + orig_end = res.end;
> + while ((res.start < res.end) && (find_next_system_ram(&res) >= 0)) {
> + pfn = (unsigned long)(res.start >> PAGE_SHIFT);
> + len = (unsigned long)(res.end + 1 - res.start) >> PAGE_SHIFT;
This needs to be
len = (unsigned long)((res.end + 1 - res.start) >> PAGE_SHIFT);
--
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:[~2007-06-15 6:05 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 6:56 [RFC] memory unplug v5 [0/6] intro KAMEZAWA Hiroyuki
2007-06-14 6:59 ` [RFC] memory unplug v5 [1/6] migration by kernel KAMEZAWA Hiroyuki
2007-06-14 7:01 ` Christoph Lameter
2007-06-14 7:11 ` KAMEZAWA Hiroyuki
2007-06-14 7:22 ` Christoph Lameter
2007-06-14 7:41 ` KAMEZAWA Hiroyuki
2007-06-14 7:47 ` Christoph Lameter
2007-06-14 8:29 ` KAMEZAWA Hiroyuki
2007-06-14 14:19 ` Christoph Lameter
2007-06-14 16:02 ` KAMEZAWA Hiroyuki
2007-06-14 16:12 ` Christoph Lameter
2007-06-14 16:15 ` KAMEZAWA Hiroyuki
2007-06-14 18:04 ` Mel Gorman
2007-06-14 22:31 ` KAMEZAWA Hiroyuki
2007-06-15 9:43 ` KAMEZAWA Hiroyuki
2007-06-15 9:53 ` KAMEZAWA Hiroyuki
2007-06-15 14:41 ` Christoph Lameter
2007-06-15 15:36 ` KAMEZAWA Hiroyuki
2007-06-14 7:00 ` [RFC] memory unplug v5 [2/6] isolate lru page race fix KAMEZAWA Hiroyuki
2007-06-14 7:01 ` [RFC] memory unplug v5 [3/6] walk memory resources assist function KAMEZAWA Hiroyuki
2007-06-15 6:05 ` David Rientjes [this message]
2007-06-15 6:11 ` KAMEZAWA Hiroyuki
2007-06-14 7:03 ` [RFC] memory unplug v5 [4/6] page isolation KAMEZAWA Hiroyuki
2007-06-15 15:46 ` Dave Hansen
2007-06-15 16:59 ` KAMEZAWA Hiroyuki
2007-06-14 7:04 ` [RFC] memory unplug v5 [5/6] page unplug KAMEZAWA Hiroyuki
2007-06-15 6:04 ` David Rientjes
2007-06-15 6:12 ` KAMEZAWA Hiroyuki
2007-06-15 14:35 ` Christoph Lameter
2007-06-15 14:40 ` Andy Whitcroft
2007-06-15 15:52 ` Dave Hansen
2007-06-15 17:03 ` KAMEZAWA Hiroyuki
2007-06-15 21:09 ` Dave Hansen
2007-06-14 7:06 ` [RFC] memory unplug v5 [6/6] ia64 interface KAMEZAWA Hiroyuki
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=alpine.DEB.0.99.0706142304530.1729@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=y-goto@jp.fujitsu.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