DPDK patches and discussions
 help / color / mirror / Atom feed
From: Michal Krawczyk <mk@semihalf.com>
To: ferruh.yigit@intel.com
Cc: shaibran@amazon.com, upstream@semihalf.com, mw@semihalf.com,
	dev@dpdk.org, Michal Krawczyk <mk@semihalf.com>
Subject: [PATCH 0/4] net/ena: v2.7.0 driver release
Date: Tue,  7 Jun 2022 18:43:37 +0200	[thread overview]
Message-ID: <20220607164341.19088-1-mk@semihalf.com> (raw)

Hi,

this patchset contains 1 generic feature support (fast mbuf free), one
improvement (simplification of the MTU verification), and 1 new device
argument which enhances the ENA user's experience by allowing them to
disable the LLQ (Low Latency Queue) mode.

Thanks,
Michal

Dawid Gorecki (2):
  net/ena: add fast mbuf free support
  net/ena: skip MTU verification

Michal Krawczyk (2):
  net/ena: add an option to disable LLQ
  net/ena: update version to 2.7.0

 doc/guides/nics/ena.rst                |   9 +++
 doc/guides/nics/features/ena.ini       |   1 +
 doc/guides/rel_notes/release_22_07.rst |   9 +++
 drivers/net/ena/ena_ethdev.c           | 105 ++++++++++++++++++-------
 drivers/net/ena/ena_ethdev.h           |   1 +
 5 files changed, 96 insertions(+), 29 deletions(-)

--
2.25.1


             reply	other threads:[~2022-06-07 16:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-07 16:43 Michal Krawczyk [this message]
2022-06-07 16:43 ` [PATCH 1/4] net/ena: add fast mbuf free support Michal Krawczyk
2022-06-07 16:43 ` [PATCH 2/4] net/ena: skip MTU verification Michal Krawczyk
2022-06-07 16:43 ` [PATCH 3/4] net/ena: add an option to disable LLQ Michal Krawczyk
2022-06-07 16:43 ` [PATCH 4/4] net/ena: update version to 2.7.0 Michal Krawczyk
2022-06-07 19:02 ` [PATCH 0/4] net/ena: v2.7.0 driver release Ferruh Yigit

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=20220607164341.19088-1-mk@semihalf.com \
    --to=mk@semihalf.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=mw@semihalf.com \
    --cc=shaibran@amazon.com \
    --cc=upstream@semihalf.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).