All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: kamezawa.hiroyu@jp.fujitsu.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] for_each_online_pgdat (take2)  [1/5]  define for_each_online_pgdat
Date: Fri, 24 Feb 2006 23:30:30 -0800	[thread overview]
Message-ID: <20060224233030.3fd18e25.akpm@osdl.org> (raw)
In-Reply-To: <20060225160736.56f9393e.kamezawa.hiroyu@jp.fujitsu.com>

KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
>
> On Sat, 25 Feb 2006 15:22:18 +0900
> KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> 
> > On Fri, 24 Feb 2006 22:16:51 -0800
> > Andrew Morton <akpm@osdl.org> wrote:
> > > 
> > > Some of these things must generate a large amount of code - would you have
> > > time to look into uninlining them, see what impact that has on .text size?
> > 
> > Okay, I'll do soon on ia64.
> > 
> I compared inlined and out-of-lined vmlinux on ia64 NUMA config kernel.
> 
> 	inline		out-of-line
> .text   005c0680        005bf6a0
> 
> 005c0680 - 005bf6a0 = FE0 = 4Kbytes. 
> 
> Considering the usage of this loop,  above size looks big ;)

Yes, we inline too many things.  Still.

> I attaches a patch which makes pgdat_walk funcs out-of-line.

Looks fine to me.

> I'll rewrite this if necessary.
> (make this patch depends on some config or move the place of funcs...)

We wouldn't want a config option for it.

And the new mmzone.c probably makes sense too - I expect there are a few
related things (page_alloc.c) which could be moved there.

  reply	other threads:[~2006-02-25  7:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-25  6:05 [PATCH] for_each_online_pgdat (take2) [1/5] define for_each_online_pgdat KAMEZAWA Hiroyuki
2006-02-25  6:16 ` Andrew Morton
2006-02-25  6:22   ` KAMEZAWA Hiroyuki
2006-02-25  7:07     ` KAMEZAWA Hiroyuki
2006-02-25  7:30       ` Andrew Morton [this message]
2006-02-25  7:38         ` 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=20060224233030.3fd18e25.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=kamezawa.hiroyu@jp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.