From: Veaceslav Falico <vfalico@redhat.com>
To: Mahesh Bandewar <maheshb@google.com>
Cc: Jay Vosburgh <fubar@us.ibm.com>,
Andy Gospodarek <andy@greyhouse.net>,
David Miller <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Eric Dumazet <edumazet@google.com>,
Maciej Zenczykowski <maze@google.com>
Subject: Re: [PATCH] bonding: Do not try to send packets over dead link in TLB mode.
Date: Wed, 9 Jul 2014 12:24:41 +0200 [thread overview]
Message-ID: <20140709102441.GB1227@redhat.com> (raw)
In-Reply-To: <1404868198-24839-1-git-send-email-maheshb@google.com>
On Tue, Jul 08, 2014 at 06:09:58PM -0700, Mahesh Bandewar wrote:
>In TLB mode if tlb_dynamic_lb is NOT set, slaves from the bond
>group are selected based on the hash distribution. This does not
>exclude dead links which are part of the bond. Also if there is a
>temporary link event which brings down the interface, packets
>hashed on that interface would be dropped too.
>
>This patch fixes these issues and distributes flows across the
>UP links only. Also the array construction of links which are
>capable of sending packets happen in the control path leaving
>only link-selection duing the data-path.
>
>One possible side effect of this is - at a link event; all
>flows will be shuffled to get good distribution. But impact of
>this should be minimum with the assumption that a member or
>members of the bond group are not available is a very temporary
>situation.
Good one, it indeed will speed up things/fix it.
Some comments:
I didn't see how you handle the case when a slave is removed (i.e.
released) from bonding.
>
>Signed-off-by: Mahesh Bandewar <maheshb@google.com>
...snip...
>+static int bond_tlb_update_slave_arr(struct bonding *bond)
>+{
>+ struct alb_bond_info *bond_info = &(BOND_ALB_INFO(bond));
>+ struct slave *tx_slave;
>+ struct list_head *iter;
>+ struct tlb_up_slave *new_arr, *old_arr;
>+
>+ new_arr = kzalloc(offsetof(struct tlb_up_slave, arr[bond->slave_cnt]),
>+ GFP_KERNEL);
>+ if (!new_arr)
>+ return -ENOMEM;
>+
>+ bond_for_each_slave(bond, tx_slave, iter) {
>+ if (bond_slave_can_tx(tx_slave))
>+ new_arr->arr[new_arr->count++] = tx_slave;
>+ }
>+
>+ spin_lock(&bond_info->slave_arr_lock);
I don't think you can re-enter bond_alb_handle_link_change(), as it's
protected either by rtnl or write-lock curr_active_slave.
>+ old_arr = bond_info->slave_arr;
>+ rcu_assign_pointer(bond_info->slave_arr, new_arr);
>+ spin_unlock(&bond_info->slave_arr_lock);
>+ if (old_arr)
>+ kfree_rcu(old_arr, rcu);
>+
>+ return 0;
>+}
...snip...
next prev parent reply other threads:[~2014-07-09 10:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 1:09 [PATCH] bonding: Do not try to send packets over dead link in TLB mode Mahesh Bandewar
2014-07-09 7:10 ` Eric Dumazet
[not found] ` <CAF2d9jh1jDL7NMZapGn_Ohy8Y2JzHrWaKA5gFgR0tU=_KydtPg@mail.gmail.com>
2014-07-09 17:09 ` Eric Dumazet
2014-07-09 17:21 ` Mahesh Bandewar
2014-07-09 10:14 ` Nikolay Aleksandrov
2014-07-09 10:24 ` Veaceslav Falico [this message]
2014-07-09 10:25 ` Nikolay Aleksandrov
2014-07-09 12:04 ` Veaceslav Falico
2014-07-09 13:17 ` Eric Dumazet
2014-07-09 13:27 ` Veaceslav Falico
2014-07-09 17:15 ` Mahesh Bandewar
2014-07-09 17:24 ` Mahesh Bandewar
2014-07-09 21:07 ` Nikolay Aleksandrov
2014-07-10 8:25 ` Maciej Żenczykowski
2014-07-09 16:52 ` Mahesh Bandewar
2014-07-10 13:39 ` Jay Vosburgh
2014-07-10 14:40 ` Mahesh Bandewar
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=20140709102441.GB1227@redhat.com \
--to=vfalico@redhat.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fubar@us.ibm.com \
--cc=maheshb@google.com \
--cc=maze@google.com \
--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).