From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <arybchenko@solarflare.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/2] net/sfc: check added but not completed descs on EF10 Tx reap
Date: Tue, 30 May 2017 13:59:42 +0100 [thread overview]
Message-ID: <d43c97c0-cc26-3137-00d6-680e200db665@intel.com> (raw)
In-Reply-To: <1495806644-32725-1-git-send-email-arybchenko@solarflare.com>
On 5/26/2017 2:50 PM, Andrew Rybchenko wrote:
> There is not point to check other Tx descriptors.
> It is important if Tx datapath does not reset Tx descriptor
> mbuf pointer to NULL on completion (EF10 simple Tx will do).
>
> Signed-off-by: Andrew Rybchenko <arybchenko@solarflare.com>
> Reviewed-by: Andy Moreton <amoreton@solarflare.com>
> Reviewed-by: David Riddoch <driddoch@solarflare.com>
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-05-30 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 13:50 Andrew Rybchenko
2017-05-26 13:50 ` [dpdk-dev] [PATCH 2/2] net/sfc: rely on one desc is one mbuf in simple " Andrew Rybchenko
2017-05-30 12:59 ` 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=d43c97c0-cc26-3137-00d6-680e200db665@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.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).