From: Thomas Monjalon <thomas@monjalon.net>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: stable@dpdk.org, dev@dpdk.org, ferruh.yigit@intel.com,
maciej.czekaj@caviumnetworks.com
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] net/thunderx: fix deadlock in Rx path
Date: Mon, 01 May 2017 22:31:46 +0200 [thread overview]
Message-ID: <3801379.4BHa0fWV0d@xps> (raw)
In-Reply-To: <20170501184155.27305-1-jerin.jacob@caviumnetworks.com>
01/05/2017 20:41, Jerin Jacob:
> RBDR buffers are refilled when SW consumes the buffers from CQ.
> This creates deadlock case when CQ buffers exhausted due to lack
> of RBDR buffers. Fix is to refill the RBDR when rx_free_thresh
> meet, irrespective of the number of CQ buffers consumed.
>
> Fixes: e2d7fc9f0a24 ("net/thunderx: add single and multi-segment Rx")
> Cc: stable@dpdk.org
>
> Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Applied, thanks
prev parent reply other threads:[~2017-05-01 20:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 18:41 [dpdk-dev] " Jerin Jacob
2017-05-01 20:31 ` Thomas Monjalon [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=3801379.4BHa0fWV0d@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=maciej.czekaj@caviumnetworks.com \
--cc=stable@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).