All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/eventdev Bug 1855] E610 vfs can't forward packets
Date: Fri, 19 Dec 2025 11:07:25 +0000	[thread overview]
Message-ID: <bug-1855-3@http.bugs.dpdk.org/> (raw)

http://bugs.dpdk.org/show_bug.cgi?id=1855

            Bug ID: 1855
           Summary: E610 vfs can't forward packets
           Product: DPDK
           Version: 24.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: eventdev
          Assignee: dev@dpdk.org
          Reporter: ktraynor@redhat.com
  Target Milestone: ---

Intel validation team reported during testing for 24.11.4 that E610 vf could
not forward packets.
https://mails.dpdk.org/archives/stable/2025-December/055158.html

They report that this is because not all patches in series here are backported.
https://patches.dpdk.org/project/dpdk/list/?series=34939&archive=both&state=*


1/3
78d6854e0e39 ("net/ixgbe: use function to check for VF")
https://git.dpdk.org/dpdk/commit/?id=78d6854e0e3941e9b37e7f5c104c2ea7576d0f45
This is just a small clean up and not really needed.

2/3
8364a0f276eb ("net/ixgbe: fix VF registers for E610")
https://git.dpdk.org/dpdk/commit/?id=8364a0f276ebc6ecb6dad1874ce0097966a74f09
This is backported to 24.11 already.

3/3
85b7d47d564f ("net/ixgbe: support MDD on VF Tx path")
https://git.dpdk.org/dpdk/commit/?id=85b7d47d564ffbe206a7d17bf5a0ed9dff17b555
This does not apply and would need rebase from Author due to conflicts.

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2025-12-19 11:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-1855-3@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=dev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.