DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Charles Myers <Charles.Myers@spirent.com>, dev@dpdk.org
Cc: Adrien Mazarguil <adrien.mazarguil@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx4: fix rx not working after mbuf alloc failure
Date: Fri, 14 Apr 2017 10:58:02 +0100	[thread overview]
Message-ID: <d260c0c4-020e-c991-dc14-920a388207e4@intel.com> (raw)
In-Reply-To: <1492121724-105935-1-git-send-email-Charles.Myers@spirent.com>

On 4/13/2017 11:15 PM, Charles Myers wrote:
> From: Charles <Charles.Myers@spirent.com>
> 
> Fixes issue where mlx4 driver stops receiving packets when mbuf
> allocation fails in mlx4_rx_burst().
> 
> This issue appears to be caused because the code doesn't recycle the
> existing mbuf to the sges array when mbuf allocation fails as is done
> in the code right above it which handles (wc.status != IBV_WC_SUCCESS).
> 
> Copying the code from the above case fixes the issue.
> 
> Fixes: acac55f16412 ("mlx4: use MOFED 3.0 fast verbs interface for Rx
> operations")

Cc: stable@dpdk.org

> 
> Signed-off-by: Charles Myers <Charles.Myers@spirent.com>

Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>

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

      reply	other threads:[~2017-04-14  9:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1492069426-123358-1-git-send-email-Charles.Myers@spirent.com>
2017-04-13  7:52 ` Myers, Charles
2017-04-13 12:05   ` Adrien Mazarguil
2017-04-13 12:22     ` Ferruh Yigit
2017-04-13 12:28       ` Adrien Mazarguil
2017-04-13 22:15   ` Charles Myers
2017-04-14  9:58     ` 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=d260c0c4-020e-c991-dc14-920a388207e4@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=Charles.Myers@spirent.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=dev@dpdk.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).