From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Takao Indoh <indou.takao@soft.fujitsu.com>, arjanv@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4]Diskdump Update
Date: Sun, 13 Jun 2004 19:08:29 -0700 [thread overview]
Message-ID: <3280000.1087178908@[10.10.2.4]> (raw)
In-Reply-To: <ACC451B04FA428indou.takao@soft.fujitsu.com>
>>> Ok, I fix it.
>>>
>>> - page = mem_map + nr;
>>> + page = pfn_to_page(nr);
>>
>> That's correct now ...
>>
>>> I also need fix this.
>>>
>>> - for (nr = 0; nr < max_mapnr; nr++) {
>>> + for (nr = 0; nr < max_pfn; nr++) {
>>
>> ... but that's not (at least AFAICS from this snippet). You need to iterate
>> over pgdats, and then over the lmem_map inside each pgdat.
>
> How about this?
>
> for_each_pgdat(pgdat) {
> for (i = 0; i < pgdat->node_spanned_pages; ++i) {
> page = pgdat->node_mem_map + i;
> ...
> }
> }
Yes, looks OK. I started writing out what it'd take to use the actual
pfn_to_page macros, but it just makes a mess ... what you have is fine.
M.
next prev parent reply other threads:[~2004-06-14 2:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 11:34 [PATCH 0/4]Diskdump Update Takao Indoh
2004-06-11 11:40 ` [PATCH 1/4]Diskdump Update Takao Indoh
2004-06-11 11:50 ` Arjan van de Ven
2004-06-11 13:40 ` Takao Indoh
2004-06-11 15:17 ` Martin J. Bligh
2004-06-14 1:38 ` Takao Indoh
2004-06-14 2:08 ` Martin J. Bligh [this message]
2004-06-21 7:59 ` Takao Indoh
2004-06-21 8:01 ` Arjan van de Ven
2004-06-22 10:57 ` Takao Indoh
2004-06-21 8:02 ` Christoph Hellwig
2004-06-11 11:41 ` [PATCH 2/4]Diskdump Update Takao Indoh
2004-06-17 12:49 ` Christoph Hellwig
2004-06-17 13:21 ` Takao Indoh
2004-06-17 13:39 ` Christoph Hellwig
2004-06-22 12:01 ` Takao Indoh
2004-06-22 12:12 ` Christoph Hellwig
2004-06-23 1:47 ` Takao Indoh
2004-06-11 11:42 ` [PATCH 3/4]Diskdump Update Takao Indoh
2004-06-11 11:43 ` [PATCH 4/4]Diskdump Update Takao Indoh
2004-06-14 14:20 ` [PATCH 0/4]Diskdump Update Takao Indoh
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='3280000.1087178908@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=arjanv@redhat.com \
--cc=indou.takao@soft.fujitsu.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®