[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20080213225555.GN12393@linux.vnet.ibm.com>
Date: Wed, 13 Feb 2008 14:55:55 -0800
From: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To: Jarek Poplawski <jarkao2@...il.com>
Cc: David Miller <davem@...emloft.net>, shemminger@...tta.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] fib_trie: rcu_assign_pointer warning fix
On Tue, Feb 12, 2008 at 08:46:30PM +0100, Jarek Poplawski wrote:
> On Tue, Feb 12, 2008 at 08:32:18PM +0100, Jarek Poplawski wrote:
> ...
> > It seems the above version of this macro uses the barrier for 0, but
> > if I miss something, or for these other: documenting reasons,
>
> ...or __builtin_constants could be used for indexing (?!),
Yep. For example:
elem[0].next = 1;
rcu_assign_index(global_index, 0);
Thanx, Paul
> > then of
> > course you are right.
>
> Jarek P.
--
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