LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: David Miller <davem@davemloft.net>
Cc: paulmck@linux.vnet.ibm.com,
	"stephen.hemminger@vyatta.com"@mail.vyatta.com,
	linux-kernel@vger.kernel.org, shemminger@vyatta.com,
	netdev@vger.kernel.org, dipankar@in.ibm.com, ego@in.ibm.com,
	herbert@gondor.apana.org.au
Subject: Re: [PATCH 1/2] remove rcu_assign_pointer(NULL) penalty with type/macro safety
Date: Wed, 13 Feb 2008 16:09:00 -0800	[thread overview]
Message-ID: <20080213160900.1a84dfe9.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080213.155738.71849437.davem@davemloft.net>

On Wed, 13 Feb 2008 15:57:38 -0800 (PST)
David Miller <davem@davemloft.net> wrote:

> From: Andrew Morton <akpm@linux-foundation.org>
> Date: Wed, 13 Feb 2008 15:52:45 -0800
> 
> > On Wed, 13 Feb 2008 15:37:44 -0800
> > "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
> > 
> > > Ah.  It does take a bit to get fib_trie into one's build -- allyesconfig
> > > doesn't cut it.
> > 
> > This is not good.  The sole purpose of allmodconfig and allyesconfig is for
> > compilation and linkage coverage testing.  Hence we should aim to get as
> > much code as possible included in those cases.
> 
> Well, in this case there is a choice, either you use one routing
> lookup datastructure or the other.  It's not purposefully being hidden
> from the everything builds :-)

oic.  yes, that is a bit of a problem.  Oh well.

`make randconfig' seems to be able to enable CONFIG_IP_FIB_TRIE about one
time in eight ;)


  reply	other threads:[~2008-02-14  0:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13 22:00 [PATCH 1/2] remove rcu_assign_pointer(NULL) penalty with type/macro safety Paul E. McKenney
2008-02-13 22:05 ` [PATCH 2/2] add rcu_assign_index() if ever needed Paul E. McKenney
2008-02-14  3:32   ` Gautham R Shenoy
2008-02-14  3:41     ` Andrew Morton
2008-02-14 17:08     ` Paul E. McKenney
2008-02-14 17:24   ` Randy Dunlap
2008-02-14 18:48     ` Paul E. McKenney
2008-02-13 22:11 ` [PATCH 1/2] remove rcu_assign_pointer(NULL) penalty with type/macro safety Andrew Morton
     [not found] ` <20080213143537.1b806790@extreme>
2008-02-13 22:41   ` Paul E. McKenney
     [not found]     ` <20080213144233.05e860cb@extreme>
2008-02-13 23:37       ` Paul E. McKenney
2008-02-13 23:51         ` Stephen Hemminger
2008-02-14  0:14           ` Paul E. McKenney
2008-02-14  0:27             ` Stephen Hemminger
2008-02-14  0:42               ` Paul E. McKenney
2008-02-14  0:53                 ` Stephen Hemminger
2008-02-14  1:34                   ` Paul E. McKenney
2008-02-14  1:37                     ` Stephen Hemminger
2008-02-13 23:52         ` Andrew Morton
2008-02-13 23:55           ` Stephen Hemminger
2008-02-13 23:57           ` David Miller
2008-02-14  0:09             ` Andrew Morton [this message]
2008-02-16  0:40 ` Andrew Morton
2008-02-16  1:23   ` Paul E. McKenney

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=20080213160900.1a84dfe9.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc="stephen.hemminger@vyatta.com"@mail.vyatta.com \
    --cc=davem@davemloft.net \
    --cc=dipankar@in.ibm.com \
    --cc=ego@in.ibm.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=shemminger@vyatta.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;
as well as URLs for NNTP newsgroup(s).