linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <haveblue@us.ibm.com>
To: Yasunori Goto <y-goto@jp.fujitsu.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-mm <linux-mm@kvack.org>
Subject: Re: [patch] bug of pgdat_list connection in init_bootmem()
Date: Wed, 28 Sep 2005 09:42:15 -0700	[thread overview]
Message-ID: <1127925735.10315.232.camel@localhost> (raw)
In-Reply-To: <20050928223844.8655.Y-GOTO@jp.fujitsu.com>

On Wed, 2005-09-28 at 22:50 +0900, Yasunori Goto wrote:
>   I would like to remove this pgdat_list, to simplify hot-add/remove
>   a node. and posted patch before.
>    http://marc.theaimsgroup.com/?l=linux-mm&m=111596924629564&w=2
>    http://marc.theaimsgroup.com/?l=linux-mm&m=111596953711780&w=2
> 
>   I would like to repost after getting performance impact by this.
>   But it is very hard that I can get time to use big NUMA machine now.
>   So, I don't know when I will be able to repost it.
> 
>   Anyway, this should be modified before remove pgdat_list.

Could you resync those to a current kernel and resend them?  I'll take
them into -mhp for a bit.

I'd be very skeptical that it would hurt performance.  If nothing else,
it just makes the pgdat smaller, and the likelyhood of having the next
bit in a bitmask and the NODE_DATA() entry in your cache is slightly
higher than some random pgdat->list.

-- Dave

--
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>

  reply	other threads:[~2005-09-28 16:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-28 13:50 Yasunori Goto
2005-09-28 16:42 ` Dave Hansen [this message]
2005-09-29  1:06   ` Yasunori Goto

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=1127925735.10315.232.camel@localhost \
    --to=haveblue@us.ibm.com \
    --cc=akpm@osdl.org \
    --cc=linux-mm@kvack.org \
    --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