From: Jakub Palider <jpa@semihalf.com>
To: dev@dpdk.org
Cc: evgenys@amazon.com, matua@amazon.com, netanel@amazon.com
Subject: [dpdk-dev] [PATCH 0/2] net/ena: check for free descriptors
Date: Sat, 29 Oct 2016 03:06:13 +0200 [thread overview]
Message-ID: <1477703175-21344-1-git-send-email-jpa@semihalf.com> (raw)
In some configurations there is mismatch between declared and actual
descriptor count which under heavy load may lead to resource shortage.
The first patch unifies the way head and tail indexes are handled and
is crucial for compactness and succeeding patch correctness.
The second patch runs check for available descriptor count.
Jakub Palider (2):
net/ena: use unmasked head/tail values
net/ena: check for free buffers prior to xmit
drivers/net/ena/ena_ethdev.c | 83 ++++++++++++++++++++++++++------------------
drivers/net/ena/ena_ethdev.h | 24 ++-----------
2 files changed, 52 insertions(+), 55 deletions(-)
--
2.5.0
next reply other threads:[~2016-10-29 1:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 1:06 Jakub Palider [this message]
2016-10-29 1:06 ` [dpdk-dev] [PATCH 1/2] net/ena: use unmasked head/tail values Jakub Palider
2016-10-29 1:06 ` [dpdk-dev] [PATCH 2/2] net/ena: check for free buffers prior to xmit Jakub Palider
2016-11-07 16:58 ` [dpdk-dev] [PATCH 0/2] net/ena: check for free descriptors Thomas Monjalon
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=1477703175-21344-1-git-send-email-jpa@semihalf.com \
--to=jpa@semihalf.com \
--cc=dev@dpdk.org \
--cc=evgenys@amazon.com \
--cc=matua@amazon.com \
--cc=netanel@amazon.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).