From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>, dev@dpdk.org
Cc: Nirranjan Kirubaharan <nirranjan@chelsio.com>,
Indranil Choudhury <indranil@chelsio.com>,
Kumar Sanghvi <kumaras@chelsio.com>
Subject: Re: [dpdk-dev] [PATCH 0/4] cxgbe: latency and performance fixes
Date: Tue, 30 May 2017 12:25:55 +0100 [thread overview]
Message-ID: <9e5fe645-b0cf-ac0f-6798-647b9d1370eb@intel.com> (raw)
In-Reply-To: <cover.1495856647.git.rahul.lakkireddy@chelsio.com>
On 5/27/2017 4:47 AM, Rahul Lakkireddy wrote:
> This series of patches rework TX and RX path to reduce latency
> and improve performance.
>
> Patch 1 reduces latency for slow traffic by using status page update
> on RX path to process batch of packets and improves coalesce TX path
> to handle slow moving traffic.
>
> Patch 2 fixes an issue with RXQ default parameters not being applied
> to all ports under same PF.
>
> Patch 3 fixes rmb bottleneck in RX path.
>
> Patch 4 adds ability to configure PCIe extended tags.
>
> This series depend on following series:
>
> "cxgbe: add support for Chelsio T6 family of adapters"
>
> Thanks,
> Rahul
>
> Rahul Lakkireddy (4):
> cxgbe: improve latency for slow traffic
> cxgbe: fix rxq default params for ports under same PF
> cxgbe: remove rmb bottleneck in RX path
> cxgbe: configure PCIe extended tags
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2017-05-30 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-27 3:47 Rahul Lakkireddy
2017-05-27 3:47 ` [dpdk-dev] [PATCH 1/4] cxgbe: improve latency for slow traffic Rahul Lakkireddy
2017-05-27 3:47 ` [dpdk-dev] [PATCH 2/4] cxgbe: fix rxq default params for ports under same PF Rahul Lakkireddy
2017-05-27 3:47 ` [dpdk-dev] [PATCH 3/4] cxgbe: remove rmb bottleneck in RX path Rahul Lakkireddy
2017-05-27 3:48 ` [dpdk-dev] [PATCH 4/4] cxgbe: configure PCIe extended tags Rahul Lakkireddy
2017-05-30 11:25 ` 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=9e5fe645-b0cf-ac0f-6798-647b9d1370eb@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=indranil@chelsio.com \
--cc=kumaras@chelsio.com \
--cc=nirranjan@chelsio.com \
--cc=rahul.lakkireddy@chelsio.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).