[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20130903083429.GC18504@redhat.com>
Date: Tue, 3 Sep 2013 10:34:29 +0200
From: Veaceslav Falico <vfalico@...hat.com>
To: Jiri Pirko <jiri@...nulli.us>
Cc: netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Alexander Duyck <alexander.h.duyck@...el.com>,
Cong Wang <amwang@...hat.com>
Subject: Re: [PATCH RFC net-next 01/21] net: add neighbour_dev_list to save
only neighbours
On Tue, Sep 03, 2013 at 10:29:43AM +0200, Jiri Pirko wrote:
>Mon, Sep 02, 2013 at 11:39:05PM CEST, vfalico@...hat.com wrote:
...snip...
>>- struct list_head upper_dev_list; /* List of upper devices */
>>- struct list_head lower_dev_list;
>>+
>>+ /* directly linked devices, like slaves for bonding */
>>+ struct {
>>+ struct list_head upper;
>>+ struct list_head lower;
>>+ } neighbour_dev_list ;
>>+
>>+ /* all linked devices, *including* neighbours */
>>+ struct {
>>+ struct list_head upper;
>>+ struct list_head lower;
>>+ } all_dev_list ;
>
>
>I think there is need for some naming consistency for functions and
>macros handling these lists.
>
>I propose:
>dev_list (drop the "neighbour") and all_dev_list
Agreed.
>
>and exported functions and macros called like:
>netdev_lower_get_next_priv()
>netdev_lower_for_each_priv()
>netdev_all_upper_get_next_rcu()
>etc...
Yep, will try to convert and see how it goes.
Thanks a lot!
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists