From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>, dev@dpdk.org
Cc: surendra@chelsio.com, shaguna@chelsio.com, indranil@chelsio.com,
nirranjan@chelsio.com
Subject: Re: [dpdk-dev] [PATCH 0/5] net/cxgbe: feature updates and bug fixes
Date: Wed, 4 Jul 2018 21:02:54 +0100 [thread overview]
Message-ID: <5d0f6d35-f142-a1d4-dc19-06bed536bad1@intel.com> (raw)
In-Reply-To: <cover.1530300158.git.rahul.lakkireddy@chelsio.com>
On 6/29/2018 8:23 PM, Rahul Lakkireddy wrote:
> Patch 1 adds link up and down operations for PF and VF.
>
> Patch 2 enables 2-tuple based RSS hash on IPv4 fragment packets and
> IPv6 packets with extension headers.
>
> Patch 3 queries firmware for max queues that can be allocated.
>
> Patch 4 fixes Rx channel map and ingress queue type needed for firmware
> to manage internal mapping correctly.
>
> Patch 5 fixes forgotten Tx byte counters for VF.
>
> Thanks,
> Rahul
>
> Rahul Lakkireddy (5):
> net/cxgbe: add link up and down ops
> net/cxgbe: enable more RSS hash functions
> net/cxgbe: query firmware for max queues available
> net/cxgbe: fix Rx channel map and queue type
> net/cxgbevf: add missing Tx byte counters
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2018-07-04 20:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 19:23 Rahul Lakkireddy
2018-06-29 19:23 ` [dpdk-dev] [PATCH 1/5] net/cxgbe: add link up and down ops Rahul Lakkireddy
2018-06-29 19:23 ` [dpdk-dev] [PATCH 2/5] net/cxgbe: enable more RSS hash functions Rahul Lakkireddy
2018-06-29 19:23 ` [dpdk-dev] [PATCH 3/5] net/cxgbe: query firmware for max queues available Rahul Lakkireddy
2018-06-29 19:23 ` [dpdk-dev] [PATCH 4/5] net/cxgbe: fix Rx channel map and queue type Rahul Lakkireddy
2018-06-29 19:23 ` [dpdk-dev] [PATCH 5/5] net/cxgbevf: add missing Tx byte counters Rahul Lakkireddy
2018-07-04 20:02 ` 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=5d0f6d35-f142-a1d4-dc19-06bed536bad1@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=indranil@chelsio.com \
--cc=nirranjan@chelsio.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=shaguna@chelsio.com \
--cc=surendra@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).