DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Zaiyu Wang" <zaiyuwang@trustnetic.com>
To: "'Stephen Hemminger'" <stephen@networkplumber.org>
Cc: <dev@dpdk.org>
Subject: RE: [PATCH v4 0/4] Wangxun fixes and new features
Date: Wed, 1 Jul 2026 10:08:21 +0800	[thread overview]
Message-ID: <005601dd08fe$7defb600$79cf2200$@trustnetic.com> (raw)
In-Reply-To: <20260630071555.0b0287b6@phoenix.local>

> On Tue, 30 Jun 2026 19:16:00 +0800
> Zaiyu Wang <zaiyuwang@trustnetic.com> wrote:
> 
> > This patchset introduces three new features and critical fixes for our
> > recent release cycle.
> >
> > Patches 1-2 add support for UDP Segmentation Offload (USO) to improve
> > large-packet transmission performance for UDP workloads.
> >
> > Patch 3 enables VFs to sense PF ifconfig down/up events, allowing
> > better fault tolerance and fast recovery in virtualized environments.
> >
> > Patch 4 adds the missing VF support for the Amber-Lite 40G NICs, which
> > was previously omitted in the initial integration.
> 
> Applied to net-next. Had to resolve a code merge conflict from earlier
> changes in net-next and also release note conflicts.
> 
Thanks.


      reply	other threads:[~2026-07-01  2:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260617105959.10764-1-zaiyuwang@trustnetic.om>
2026-06-30 11:16 ` [PATCH v4 0/4] Wangxun fixes and new features Zaiyu Wang
2026-06-30 11:16   ` [PATCH v4 1/4] net/ngbe: implement USO support Zaiyu Wang
2026-06-30 11:16   ` [PATCH v4 2/4] net/txgbe: " Zaiyu Wang
2026-06-30 11:16   ` [PATCH v4 3/4] net/txgbe: add support for VF sensing PF down Zaiyu Wang
2026-06-30 11:16   ` [PATCH v4 4/4] net/txgbe: add VF support for Amber-Lite 40G NIC Zaiyu Wang
2026-06-30 14:15   ` [PATCH v4 0/4] Wangxun fixes and new features Stephen Hemminger
2026-07-01  2:08     ` Zaiyu Wang [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='005601dd08fe$7defb600$79cf2200$@trustnetic.com' \
    --to=zaiyuwang@trustnetic.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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