From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/6] bnxt patchset for Tx performance optimization
Date: Mon, 27 May 2019 17:16:57 +0100 [thread overview]
Message-ID: <a9ea14cd-3f6c-fdb3-2c68-042e1b38d963@intel.com> (raw)
In-Reply-To: <20190515180817.71523-1-ajit.khaparde@broadcom.com>
On 5/15/2019 7:08 PM, Ajit Khaparde wrote:
> This patchset brings in few fixes and some changes tuning
> the Tx datapath performance in bnxt PMD.
> Please apply.
>
> Ajit Khaparde (4):
> net/bnxt: fix an issue seen with TSO
> net/bnxt: add support to update ipid
> net/bnxt: check for some error conditions in Tx path
> net/bnxt: support bulk free of Tx mbufs
>
> Sriharsha Basavapatna (2):
> net/bnxt: fix a couple of issues with Tx batching
> net/bnxt: optimize Tx batching code
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-05-27 16:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-15 18:08 Ajit Khaparde
2019-05-15 18:08 ` Ajit Khaparde
2019-05-15 18:08 ` [dpdk-dev] [PATCH 1/6] net/bnxt: fix an issue seen with TSO Ajit Khaparde
2019-05-15 18:08 ` Ajit Khaparde
2019-05-15 18:08 ` [dpdk-dev] [PATCH 2/6] net/bnxt: add support to update ipid Ajit Khaparde
2019-05-15 18:08 ` Ajit Khaparde
2019-05-15 18:08 ` [dpdk-dev] [PATCH 3/6] net/bnxt: check for some error conditions in Tx path Ajit Khaparde
2019-05-15 18:08 ` Ajit Khaparde
2019-05-15 18:08 ` [dpdk-dev] [PATCH 4/6] net/bnxt: fix a couple of issues with Tx batching Ajit Khaparde
2019-05-15 18:08 ` Ajit Khaparde
2019-05-15 18:08 ` [dpdk-dev] [PATCH 5/6] net/bnxt: optimize Tx batching code Ajit Khaparde
2019-05-15 18:08 ` Ajit Khaparde
2019-05-15 18:08 ` [dpdk-dev] [PATCH 6/6] net/bnxt: support bulk free of Tx mbufs Ajit Khaparde
2019-05-15 18:08 ` Ajit Khaparde
2019-05-27 16:16 ` 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=a9ea14cd-3f6c-fdb3-2c68-042e1b38d963@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ajit.khaparde@broadcom.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).