From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jakub Palider <jpa@semihalf.com>
Cc: dev@dpdk.org, evgenys@amazon.com, matua@amazon.com, netanel@amazon.com
Subject: Re: [dpdk-dev] [PATCH 0/2] net/ena: check for free descriptors
Date: Mon, 07 Nov 2016 17:58:39 +0100 [thread overview]
Message-ID: <1726336.HacXeD4S0N@xps13> (raw)
In-Reply-To: <1477703175-21344-1-git-send-email-jpa@semihalf.com>
2016-10-29 03:06, Jakub Palider:
> 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
Applied, thanks
prev parent reply other threads:[~2016-11-07 16:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 1:06 Jakub Palider
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 ` 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=1726336.HacXeD4S0N@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=evgenys@amazon.com \
--cc=jpa@semihalf.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).