From: "John Daley (johndale)" <johndale@cisco.com>
To: Kevin Traynor <ktraynor@redhat.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v2 00/15] enic PMD fixes and performance improvements
Date: Wed, 25 Jul 2018 19:46:12 +0000 [thread overview]
Message-ID: <90259559d5f3494f878f5b987add67b3@XCH-RCD-007.cisco.com> (raw)
In-Reply-To: <dd52087f-d889-a319-7057-6a91be325f97@redhat.com>
Hi Kevin,
Inline.
-john
> -----Original Message-----
> From: Kevin Traynor <ktraynor@redhat.com>
> Sent: Wednesday, July 25, 2018 11:37 AM
> To: John Daley (johndale) <johndale@cisco.com>; ferruh.yigit@intel.com
> Cc: dev@dpdk.org; stable@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v2 00/15] enic PMD fixes and performance
> improvements
>
> On 06/29/2018 10:29 AM, John Daley wrote:
> > Updated a few commits in the patchset per suggestions by Ferrus Yigit.
> > thanks,
> > John
> >
> > Hyong Youb Kim (12):
> > net/enic: fix receive packet types
> > net/enic: update the UDP RSS detection mechanism
> > net/enic: do not overwrite admin Tx queue limit
> > net/enic: initialize RQ fetch index before enabling RQ
> > net/enic: report ring limits and preferred default values
> > net/enic: add devarg to specify ingress VLAN rewrite mode
> > net/enic: add handlers to add/delete vxlan port number
> > net/enic: use mbuf pointer array for inflight Tx packets
> > net/enic: support mbuf fast free offload
> > net/enic: reduce Tx completion updates
> > net/enic: add the simple version of Tx handler
> > net/enic: check maximum packet size in Tx prepare handler
> >
> > John Daley (3):
> > net/enic: add simple Rx handler
> > net/enic: cap Rx packet processing to end of desc ring
> > doc: update release notes with new enic features
> >
>
> Hi John, seems like many of these would be candidates for stable branches?
Yes, a few of them. We will backport, test and submit to the stable branches as soon as we are done with 18.08 testing.
Thanks,
John
>
> > doc/guides/nics/enic.rst | 15 +-
> > doc/guides/nics/features/enic.ini | 1 +
> > doc/guides/rel_notes/release_18_08.rst | 8 +
> > drivers/net/enic/base/cq_desc.h | 1 +
> > drivers/net/enic/base/vnic_dev.c | 16 ++
> > drivers/net/enic/base/vnic_dev.h | 4 +
> > drivers/net/enic/base/vnic_devcmd.h | 23 ++-
> > drivers/net/enic/base/vnic_enet.h | 5 +-
> > drivers/net/enic/base/vnic_nic.h | 4 +-
> > drivers/net/enic/base/vnic_rq.h | 2 +
> > drivers/net/enic/base/vnic_wq.c | 9 +-
> > drivers/net/enic/base/vnic_wq.h | 12 +-
> > drivers/net/enic/enic.h | 12 ++
> > drivers/net/enic/enic_compat.h | 5 +
> > drivers/net/enic/enic_ethdev.c | 168 +++++++++++++++--
> > drivers/net/enic/enic_main.c | 125 ++++++++++---
> > drivers/net/enic/enic_res.c | 13 +-
> > drivers/net/enic/enic_res.h | 16 ++
> > drivers/net/enic/enic_rxtx.c | 333 +++++++++++++++++++++++++++++---
> -
> > 19 files changed, 668 insertions(+), 104 deletions(-)
> >
prev parent reply other threads:[~2018-07-25 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180628031940.17397-1-johndale@cisco.com>
[not found] ` <20180629092944.15576-1-johndale@cisco.com>
2018-07-25 18:37 ` Kevin Traynor
2018-07-25 19:46 ` John Daley (johndale) [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=90259559d5f3494f878f5b987add67b3@XCH-RCD-007.cisco.com \
--to=johndale@cisco.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ktraynor@redhat.com \
--cc=stable@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).