[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080213160900.1a84dfe9.akpm@linux-foundation.org>
Date: Wed, 13 Feb 2008 16:09:00 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: David Miller <davem@...emloft.net>
Cc: paulmck@...ux.vnet.ibm.com,
"stephen.hemminger@...tta.com"@mail.vyatta.com,
linux-kernel@...r.kernel.org, shemminger@...tta.com,
netdev@...r.kernel.org, dipankar@...ibm.com, ego@...ibm.com,
herbert@...dor.apana.org.au
Subject: Re: [PATCH 1/2] remove rcu_assign_pointer(NULL) penalty with
type/macro safety
On Wed, 13 Feb 2008 15:57:38 -0800 (PST)
David Miller <davem@...emloft.net> wrote:
> From: Andrew Morton <akpm@...ux-foundation.org>
> Date: Wed, 13 Feb 2008 15:52:45 -0800
>
> > On Wed, 13 Feb 2008 15:37:44 -0800
> > "Paul E. McKenney" <paulmck@...ux.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 ;)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists