From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: linux-mm@kvack.org
Subject: [PATCH/RFC 0/2] Remove pgdat list
Date: Fri, 13 May 2005 16:25:56 +0900 [thread overview]
Message-ID: <20050513160538.5225.Y-GOTO@jp.fujitsu.com> (raw)
Hello.
I wrote patches to remove pgdat list in pgdat structure, because
I think it is redundant.
In the current implementation, pgdat structure has this list.
struct pglist_data{
:
struct pglist_data *pgdat_next;
:
}
This is used for searching other zones and nodes by for_each_pgdat and
for_each_zone macros. So, if a node is hot added,
the system has to not only set bit of node_online_map,
but also connect this for new node.
However, all of pgdat list user would like to know just
next (online) node. So, I think node_online_map is enough information
for them to find other nodes.
By this patch, hot add/remove code for node will be a little simpler.
This patches is for 2.6.12-rc3-mhp1. I tested them on Tiger4 with
node emulation.
Please comment.
Thanks.
--
Yasunori Goto
--
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:[~2005-05-13 7:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050513160538.5225.Y-GOTO@jp.fujitsu.com \
--to=y-goto@jp.fujitsu.com \
--cc=linux-mm@kvack.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