netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Veaceslav Falico <vfalico@redhat.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: netdev@vger.kernel.org, jiri@resnulli.us,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Alexander Duyck <alexander.h.duyck@intel.com>
Subject: Re: [PATCH v3 net-next 21/27] net: add a function to get the next private
Date: Tue, 17 Sep 2013 15:55:07 +0200	[thread overview]
Message-ID: <20130917135507.GD2929@redhat.com> (raw)
In-Reply-To: <1379382601.23881.36.camel@deadeye.wl.decadent.org.uk>

On Tue, Sep 17, 2013 at 02:50:01AM +0100, Ben Hutchings wrote:
>On Tue, 2013-09-17 at 02:46 +0200, Veaceslav Falico wrote:
>> It searches for the provided private and returns the next one. If private
>> is not found or next list element is list head - returns NULL.
>
>This is going to take linear time, which is probably OK for a bond that
>has only a very few devices.  But it would likely be a really bad idea
>for, say, a bridge device that could have tens or hundreds of lower
>devices.  So it's not a generically useful function.

Indeed, you're right. I've tried searching or trying to figure out why
others could need it - with no luck. It's really bonding-specific. And, in
any case, if there will be more users of it - it can be changed in the
future.

>
>I think the bonding driver can implement this:
>
>[...]
>> --- a/net/core/dev.c
>> +++ b/net/core/dev.c
>> @@ -5055,6 +5055,33 @@ void *netdev_lower_dev_get_private(struct net_device *dev,
>>  }
>>  EXPORT_SYMBOL(netdev_lower_dev_get_private);
>>
>> +/* netdev_lower_dev_get_next_private - return the ->private of the list
>> + *				       element whos ->private == private.
>> + * @dev - device to search
>> + * @private - private pointer to search for.
>> + *
>> + * Returns the next ->private pointer, if ->next is not head and private is
>> + * found.
>> + */
>> +extern void *netdev_lower_dev_get_next_private(struct net_device *dev,
>> +					       void *private)
>> +{
>> +	struct netdev_adjacent *lower;
>> +
>> +	list_for_each_entry(lower, &dev->adj_list.lower, list) {
>> +		if (lower->private == private) {
>> +			lower = list_entry(lower->list.next,
>> +					   struct netdev_adjacent, list);
>> +			if (&lower->list == &dev->adj_list.lower)
>> +				return NULL;
>> +			return lower->private;
>> +		}
>> +	}
>> +
>> +	return NULL;
>> +}
>> +EXPORT_SYMBOL(netdev_lower_dev_get_next_private);
>
>using only the functions already exported:
>
>static void *__bond_next_slave(struct net_device *dev, void *private)
>{
>	struct list_head *iter;
>	struct net_device *lower;
>	bool found = false;
>
>	netdev_for_each_lower_dev(dev, lower, iter) {
>		if (found)
>			return netdev_adjacent_get_private(iter);
>		if (netdev_adjacent_get_private(iter) == private)
>			found = true;
>	}
>
>	return NULL;
>}
>
>(not that I've tested it :-).

Yep, I'll think of something like that and send it in the next version,
dropping the current netdev_ variant.

Thanks a lot!

>
>Ben.
>
>> +
>>  static void dev_change_rx_flags(struct net_device *dev, int flags)
>>  {
>>  	const struct net_device_ops *ops = dev->netdev_ops;
>
>-- 
>Ben Hutchings, Staff Engineer, Solarflare
>Not speaking for my employer; that's the marketing department's job.
>They asked us to note that Solarflare product names are trademarked.
>

  reply	other threads:[~2013-09-17 13:56 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17  0:46 [PATCH v3 net-next 00/27] bonding: use neighbours instead of own lists Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 01/27] net: add adj_list to save only neighbours Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 02/27] net: add RCU variant to search for netdev_adjacent link Veaceslav Falico
2013-09-17  1:23   ` Ben Hutchings
2013-09-17  7:34     ` Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 03/27] net: uninline netdev neighbour functions Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 04/27] net: add netdev_adjacent->private and allow to use it Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 05/27] bonding: populate neighbour's private on enslave Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 06/27] bonding: modify bond_get_slave_by_dev() to use neighbours Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 07/27] net: add for_each iterators through neighbour lower link's private Veaceslav Falico
2013-09-17  1:26   ` Ben Hutchings
2013-09-17  7:36     ` Veaceslav Falico
2013-09-17 11:43       ` Eric Dumazet
2013-09-17 12:29         ` Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 08/27] bonding: remove bond_for_each_slave_continue_reverse() Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 09/27] bonding: make bond_for_each_slave() use lower neighbour's private Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 10/27] bonding: use bond_for_each_slave() in bond_uninit() Veaceslav Falico
2013-09-18  9:53   ` Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 11/27] bonding: rework bond_3ad_xmit_xor() to use bond_for_each_slave() only Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 12/27] bonding: rework rlb_next_rx_slave() to use bond_for_each_slave() Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 13/27] bonding: rework bond_find_best_slave() " Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 14/27] bonding: rework bond_ab_arp_probe() " Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 15/27] bonding: remove unused bond_for_each_slave_from() Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 16/27] bonding: add bond_has_slaves() and use it Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 17/27] bonding: convert bond_has_slaves() to use the neighbour list Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 18/27] net: add a possibility to get private from netdev_adjacent->list Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 19/27] bonding: convert first/last slave logic to use neighbours Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 20/27] bonding: remove bond_prev_slave() Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 21/27] net: add a function to get the next private Veaceslav Falico
2013-09-17  1:50   ` Ben Hutchings
2013-09-17 13:55     ` Veaceslav Falico [this message]
2013-09-17  0:46 ` [PATCH v3 net-next 22/27] bonding: use neighbours for bond_next_slave() Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 23/27] bonding: remove slave lists Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 24/27] vlan: link the upper neighbour only after registering Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 25/27] vlan: unlink the upper neighbour before unregistering Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 26/27] net: expose the master link to sysfs, and remove it from bond Veaceslav Falico
2013-09-17  0:46 ` [PATCH v3 net-next 27/27] net: create sysfs symlinks for neighbour devices Veaceslav Falico

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=20130917135507.GD2929@redhat.com \
    --to=vfalico@redhat.com \
    --cc=alexander.h.duyck@intel.com \
    --cc=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jiri@resnulli.us \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).