DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Frank Dressler <frank@dressler.pro>
Cc: dev@dpdk.org, thomas@monjalon.net, david.marchand@redhat.com,
	ktraynor@redhat.com, Bing Zhao <bingz@nvidia.com>
Subject: Re: [PATCH] net/af_packet: fix build with old kernel headers
Date: Sun, 8 Nov 2026 12:29:29 -0800	[thread overview]
Message-ID: <20261108122929.38561d27@phoenix.local> (raw)
In-Reply-To: <dab30cb4-025c-4a75-892d-3519dcc67053@dressler.pro>

On Sun, 8 Nov 2026 18:51:35 +0000
Frank Dressler <frank@dressler.pro> wrote:

> But should these changes go into DPDK or NVIDIA's DOCA?
> 
> DPDK's current code requires no patch since the code works with the 
> kernel versions required by DPDK, i.e. Linux >= v5.4.
> 
> NVIDIA's DOCA, however, ships current DPDK to RHEL 8 which comes with 
> kernel v4.18 that is unsupported since DPDK v24.07. The latest release 
> is DOCA 3.5.0 which ships DPDK v26.03 to RHEL 8 which is not supported 
> by DPDK.

If NVIDIA is shipping new DPDK with old distro, then it is there problem.

  reply	other threads:[~2026-11-08 20:29 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-06 14:27 [PATCH] net/af_packet: fix build with old kernel headers Bing Zhao
2026-11-06 14:46 ` Thomas Monjalon
2026-11-06 16:06 ` Frank Dressler
2026-11-07 11:11   ` Frank Dressler
2026-11-08 16:22     ` Stephen Hemminger
2026-11-08 18:51       ` Frank Dressler
2026-11-08 20:29         ` Stephen Hemminger [this message]
2026-11-09 15:47 ` [PATCH v2] " Bing Zhao
2026-11-09 17:47   ` Stephen Hemminger
2026-11-10 10:39     ` Thomas Monjalon
2026-11-10 12:52       ` Frank Dressler
2026-11-10 13:56         ` Thomas Monjalon
2026-11-10 14:23           ` Frank Dressler
2026-11-10 16:51   ` Stephen Hemminger

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=20261108122929.38561d27@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=bingz@nvidia.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=frank@dressler.pro \
    --cc=ktraynor@redhat.com \
    --cc=thomas@monjalon.net \
    /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