DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: "Deng, KaiwenX" <kaiwenx.deng@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"Yang, Qiming" <qiming.yang@intel.com>,
	"Zhou, YidingX" <yidingx.zhou@intel.com>,
	Ting Xu <ting.xu@intel.com>, Kevin Liu <kevinx.liu@intel.com>,
	Ajit Khaparde <ajit.khaparde@broadcom.com>,
	 Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Jerin Jacob <jerinj@marvell.com>,
	Hemant Agrawal <hemant.agrawal@nxp.com>,
	Somnath Kotur <somnath.kotur@broadcom.com>,
	"Zhang, Qi Z" <qi.z.zhang@intel.com>,
	david.marchand@redhat.com
Subject: Re: [PATCH v2] net/ice: fix tso tunnel setting to not take effect
Date: Mon, 22 Jan 2024 12:43:20 +0100	[thread overview]
Message-ID: <15118360.tv2OnDr8pf@thomas> (raw)
In-Reply-To: <DM4PR11MB5994541B8AFD086FF327636CD79FA@DM4PR11MB5994.namprd11.prod.outlook.com>

> > The Tx offload capabilities of ICE ethdev doesn't include tso tunnel, which will
> > result in tso tunnel setting to not take effect.
> > 
> > The patch adds tunnel tso offload to ICE_TX_NO_VECTOR_FLAGS.
> > 
> > This commit will add tso tunnel capabilities in ice_dev_info_get().
> > 
> > Bugzilla ID: 1327
> > Fixes: d852fec1be63 ("net/ice: fix Tx offload path choice")
> > Fixes: 295968d17407 ("ethdev: add namespace")
> > Cc: stable@dpdk.org
> > 
> > Signed-off-by: Kaiwen Deng <kaiwenx.deng@intel.com>
> 
> Acked-by: Qi Zhang <qi.z.zhang@intel.com>
> 
> Applied to dpdk-next-net-intel.

As said by David in v1, 295968d17407 ("ethdev: add namespace") is not a cause.
Removing while pulling.



      reply	other threads:[~2024-01-22 11:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-24  6:44 [PATCH] " Kaiwen Deng
2023-11-24  7:50 ` lihuisong (C)
2023-11-24  8:02 ` David Marchand
2023-12-07  2:30 ` [PATCH v2] " Kaiwen Deng
2023-12-27 11:20   ` Zhang, Qi Z
2024-01-22 11:43     ` Thomas Monjalon [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=15118360.tv2OnDr8pf@thomas \
    --to=thomas@monjalon.net \
    --cc=ajit.khaparde@broadcom.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=jerinj@marvell.com \
    --cc=kaiwenx.deng@intel.com \
    --cc=kevinx.liu@intel.com \
    --cc=qi.z.zhang@intel.com \
    --cc=qiming.yang@intel.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=stable@dpdk.org \
    --cc=ting.xu@intel.com \
    --cc=yidingx.zhou@intel.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).