DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xu, HailinX" <hailinx.xu@intel.com>
To: "skori@marvell.com" <skori@marvell.com>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	"Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH] net/ice: set pkt prepare to dummy instead of NULL
Date: Tue, 11 Nov 2025 01:48:01 +0000	[thread overview]
Message-ID: <IA3PR11MB9040359D3E6719465C88155F9FCFA@IA3PR11MB9040.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20251110122457.2575615-1-skori@marvell.com>

> -----Original Message-----
> From: skori@marvell.com <skori@marvell.com>
> Sent: Monday, November 10, 2025 8:25 PM
> To: Richardson, Bruce <bruce.richardson@intel.com>; Burakov, Anatoly
> <anatoly.burakov@intel.com>
> Cc: dev@dpdk.org; Sunil Kumar Kori <skori@marvell.com>
> Subject: [PATCH] net/ice: set pkt prepare to dummy instead of NULL
> 
> From: Sunil Kumar Kori <skori@marvell.com>
> 
> As per recent change by the following commit:
> 
> commit 066f3d9cc21c ("ethdev: remove callback checks from fast path")
> 
> framework unconditionally invokes dev->tx_pkt_prepare.
> Due to this, ICE driver gets crashed as tx_pkt_prepare was set to NULL during
> initialization.
> 
> Ensure dev->tx_pkt_prepare is not NULL when vector or simple TX paths are
> selected, by assigning rte_eth_tx_pkt_prepare_dummy.
> 
> This aligns with expectations with above mentioned commit.
> 
> Bugzilla ID: 1795
> 
> Signed-off-by: Sunil Kumar Kori <skori@marvell.com>
> ---
Tested-by: Xu, HailinX <hailinx.xu@intel.com>

      reply	other threads:[~2025-11-11  1:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-10 12:24 skori
2025-11-11  1:48 ` Xu, HailinX [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=IA3PR11MB9040359D3E6719465C88155F9FCFA@IA3PR11MB9040.namprd11.prod.outlook.com \
    --to=hailinx.xu@intel.com \
    --cc=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=skori@marvell.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).