From: "Deng, KaiwenX" <kaiwenx.deng@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>,
Yaroslav Brustinov <ybrustin@cisco.com>
Subject: RE: [PATCH] net/intel: fix igb tx queue offloads capability
Date: Wed, 7 May 2025 08:59:04 +0000 [thread overview]
Message-ID: <IA1PR11MB7853D99DFF2993A5E3F1C4828E88A@IA1PR11MB7853.namprd11.prod.outlook.com> (raw)
In-Reply-To: <aA-c2XuK7SFVKqqZ@bricha3-mobl1.ger.corp.intel.com>
> -----Original Message-----
> From: Richardson, Bruce <bruce.richardson@intel.com>
> Sent: Monday, April 28, 2025 11:21 PM
> To: Deng, KaiwenX <kaiwenx.deng@intel.com>
> Cc: dev@dpdk.org; stable@dpdk.org; Zhang, Qi Z <qi.z.zhang@intel.com>;
> Yaroslav Brustinov <ybrustin@cisco.com>
> Subject: Re: [PATCH] net/intel: fix igb tx queue offloads capability
>
> On Mon, Apr 14, 2025 at 04:53:52PM +0800, Kaiwen Deng wrote:
> > The igb driver assigns the tx port offload capability to the tx queue
> > offload capability.
> >
> > This commit will fix this issue.
> >
> > Fixes: daa3b0833f08 ("net/e1000: fix Tx offload capability typos")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Kaiwen Deng <kaiwenx.deng@intel.com>
> > ---
> > drivers/net/intel/e1000/igb_rxtx.c | 6 ++----
> > 1 file changed, 2 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/net/intel/e1000/igb_rxtx.c
> > b/drivers/net/intel/e1000/igb_rxtx.c
> > index 4276bb6d31..b63de2354f 100644
> > --- a/drivers/net/intel/e1000/igb_rxtx.c
> > +++ b/drivers/net/intel/e1000/igb_rxtx.c
> > @@ -1490,11 +1490,9 @@ igb_get_tx_port_offloads_capa(struct
> > rte_eth_dev *dev) uint64_t igb_get_tx_queue_offloads_capa(struct
> > rte_eth_dev *dev) {
> > - uint64_t tx_queue_offload_capa;
> > -
> > - tx_queue_offload_capa = igb_get_tx_port_offloads_capa(dev);
> > + RTE_SET_USED(dev);
> >
> > - return tx_queue_offload_capa;
> > + return 0;
> > }
> >
>
> I suspect there may be more instances in the code where we do this. For
> example, I see the same pattern used in em_rxtx.c in e1000. Can you quickly
> check our other drivers to see if the same mistake is repeated elsewhere other
> than "igb" and "em"?
Hi Bruce,
After checking, the same error is not repeated anywhere else except on "igb" and "em" .
However, I noticed that there is only one txq available for the "em" device, and according
to the comments in the code, This design may be intentional, as port offloading and queue
offloading are practically the same in the case of only one txq.
>
> /Bruce
prev parent reply other threads:[~2025-05-07 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 8:53 Kaiwen Deng
2025-04-28 15:20 ` Bruce Richardson
2025-05-07 8:59 ` Deng, KaiwenX [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=IA1PR11MB7853D99DFF2993A5E3F1C4828E88A@IA1PR11MB7853.namprd11.prod.outlook.com \
--to=kaiwenx.deng@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=stable@dpdk.org \
--cc=ybrustin@cisco.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).