DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Declan Doherty <declan.doherty@intel.com>, dev@dpdk.org
Cc: klarose@sandvine.com
Subject: Re: [dpdk-dev] [PATCH] net/bond: don't drop lacpdu's on slaves tx failure
Date: Wed, 6 Dec 2017 17:17:55 -0800	[thread overview]
Message-ID: <6d7ee01e-0724-4068-61fd-dd9c942a4624@intel.com> (raw)
In-Reply-To: <20171130232535.27835-1-declan.doherty@intel.com>

On 11/30/2017 3:25 PM, Declan Doherty wrote:
> In message (http://dpdk.org/ml/archives/dev/2017-November/081557.html)
> it was noted that under congestion that the LACPDU's are dropped under
> load.
> 
> This patch changes the drop logic to re-enqueue the LACPDU to the slaves
> control message queue. This will allow resend attempt's to be made in
> subsequent tx_burst() calls on the bonded device.
> 
> Signed-off-by: Declan Doherty <declan.doherty@intel.com>

Applied to dpdk-next-net/master, thanks.

      reply	other threads:[~2017-12-07  1:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30 23:25 Declan Doherty
2017-12-07  1:17 ` Ferruh Yigit [this message]

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=6d7ee01e-0724-4068-61fd-dd9c942a4624@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=klarose@sandvine.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).