The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Christoph Lameter <clameter@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [2.6 patch] slub.c:early_kmem_cache_node_alloc() shouldn't be __init
Date: Tue, 10 Jul 2007 21:01:23 +0200	[thread overview]
Message-ID: <20070710190123.GB3492@stusta.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0707101132110.11882@schroedinger.engr.sgi.com>

On Tue, Jul 10, 2007 at 11:33:15AM -0700, Christoph Lameter wrote:
> On Tue, 10 Jul 2007, Adrian Bunk wrote:
> 
> > This patch fixes the following section mismatch:
> 
> Nack.
> 
> Can you remove the warning? early_kmem_cache_node_alloc is only used 
> during bootstrap. But it is called from a function that is also used 
> later.

The alternative is "noinline __init_refok" - the noinline is required 
because modern gcc versions already make it non-__init by inlining it 
into init_kmem_cache_nodes() without.

But I'm not convinced it's really worth manually forcing noinline only 
for moving a few bytes to __init in the CONFIG_NUMA=y case - in the  
long term this will only bit rot.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2007-07-10 19:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-10 12:44 [2.6 patch] slub.c:early_kmem_cache_node_alloc() shouldn't be __init Adrian Bunk
2007-07-10 18:33 ` Christoph Lameter
2007-07-10 19:01   ` Adrian Bunk [this message]
2007-07-10 19:43     ` Christoph Lameter

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=20070710190123.GB3492@stusta.de \
    --to=bunk@stusta.de \
    --cc=clameter@sgi.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