From: "Doherty, Declan" <declan.doherty@intel.com>
To: John Daley <johndale@cisco.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Nelson Escobar <neescoba@cisco.com>
Subject: Re: [dpdk-dev] [PATCH] bonding: fix bond link detect in non-interrupt mode
Date: Fri, 1 Apr 2016 08:00:48 +0000 [thread overview]
Message-ID: <345C63BAECC1AD42A2EC8C63AFFC3ADC2815E341@irsmsx105.ger.corp.intel.com> (raw)
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of John Daley
> Sent: Saturday, March 26, 2016 12:45 AM
> To: dev@dpdk.org
> Cc: Nelson Escobar <neescoba@cisco.com>; John Daley <johndale@cisco.com>
> Subject: [dpdk-dev] [PATCH] bonding: fix bond link detect in non-interrupt mode
>
> From: Nelson Escobar <neescoba@cisco.com>
>
> Stopping then re-starting a bond interface containing slaves that
> used polling for link detection caused the bond to think all slave
> links were down and inactive.
>
> Move the start of the polling for link from slave_add() to
> bond_ethdev_start() and in bond_ethdev_stop() make sure we clear
> the last_link_status of the slaves.
>
> Signed-off-by: Nelson Escobar <neescoba@cisco.com>
> Signed-off-by: John Daley <johndale@cisco.com>
> ---
.....
> --
> 2.7.0
Acked-by: Declan Doherty <declan.doherty@intel.com>
next reply other threads:[~2016-04-01 8:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 8:00 Doherty, Declan [this message]
2016-04-01 13:15 ` Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2016-03-26 0:44 John Daley
2016-03-30 16:15 ` Thomas Monjalon
2016-03-31 13:40 ` Thomas Monjalon
2016-03-31 17:33 ` Nelson Escobar
2016-04-01 13:35 ` Declan Doherty
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=345C63BAECC1AD42A2EC8C63AFFC3ADC2815E341@irsmsx105.ger.corp.intel.com \
--to=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=johndale@cisco.com \
--cc=neescoba@cisco.com \
/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).