DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Xu, Ke1" <ke1.xu@intel.com>,
	"Ye, MingjinX" <mingjinx.ye@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	"Zhou, YidingX" <yidingx.zhou@intel.com>,
	"Ye, MingjinX" <mingjinx.ye@intel.com>,
	"Yang, Qiming" <qiming.yang@intel.com>,
	Somnath Kotur <somnath.kotur@broadcom.com>,
	"Matz, Olivier" <olivier.matz@6wind.com>,
	Ajit Khaparde <ajit.khaparde@broadcom.com>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Subject: RE: [PATCH v2] net/ice: support vxlan gpe tunnel offload
Date: Mon, 24 Oct 2022 03:37:12 +0000	[thread overview]
Message-ID: <DM4PR11MB59943570F98197021C0F58D8D72E9@DM4PR11MB5994.namprd11.prod.outlook.com> (raw)
In-Reply-To: <PH7PR11MB605605FA0F3C4B9677E00844D32D9@PH7PR11MB6056.namprd11.prod.outlook.com>



> -----Original Message-----
> From: Xu, Ke1 <ke1.xu@intel.com>
> Sent: Friday, October 21, 2022 5:14 PM
> To: Ye, MingjinX <mingjinx.ye@intel.com>; dev@dpdk.org
> Cc: stable@dpdk.org; Zhou, YidingX <yidingx.zhou@intel.com>; Ye, MingjinX
> <mingjinx.ye@intel.com>; Yang, Qiming <qiming.yang@intel.com>; Zhang, Qi
> Z <qi.z.zhang@intel.com>; Somnath Kotur <somnath.kotur@broadcom.com>;
> Matz, Olivier <olivier.matz@6wind.com>; Ajit Khaparde
> <ajit.khaparde@broadcom.com>; Andrew Rybchenko
> <andrew.rybchenko@oktetlabs.ru>
> Subject: RE: [PATCH v2] net/ice: support vxlan gpe tunnel offload
> 
> 
> 
> > -----Original Message-----
> > From: Mingjin Ye <mingjinx.ye@intel.com>
> > Sent: Friday, October 21, 2022 9:00 PM
> > To: dev@dpdk.org
> > Cc: stable@dpdk.org; Zhou, YidingX <yidingx.zhou@intel.com>; Ye,
> > MingjinX <mingjinx.ye@intel.com>; Yang, Qiming
> > <qiming.yang@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>; Somnath
> > Kotur <somnath.kotur@broadcom.com>; Matz, Olivier
> > <olivier.matz@6wind.com>; Ajit Khaparde
> <ajit.khaparde@broadcom.com>;
> > Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
> > Subject: [PATCH v2] net/ice: support vxlan gpe tunnel offload
> >
> > PMD tx path does not support VXLAN_GPE tunnel offload. Because it does
> > not process RTE_MBUF_F_TX_TUNNEL_VXLAN_GPE flag in mbuf, and then
> the
> > "L4TUNT"
> > field will not be set in Tx context descriptor.
> >
> > This patch is to add the RTE_MBUF_F_TX_TUNNEL_VXLAN_GPE flag to
> > support Tx VXLAN_GPE offload under the scenario if the offload tso and
> > VXLAN_GPE tunnel are both required, so that it would avoid tx queue
> > overflowing.
> >
> > Fixes: daa02b5cddbb ("mbuf: add namespace to offload flags")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Mingjin Ye <mingjinx.ye@intel.com>
> 
> Verified and passed.
> Tested-by: Ke Xu <ke1.xu@intel.com>

Applied to dpdk-next-net-intel.

Thanks
Qi


      reply	other threads:[~2022-10-24  3:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21 12:59 Mingjin Ye
2022-10-21  9:14 ` Xu, Ke1
2022-10-24  3:37   ` Zhang, Qi Z [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=DM4PR11MB59943570F98197021C0F58D8D72E9@DM4PR11MB5994.namprd11.prod.outlook.com \
    --to=qi.z.zhang@intel.com \
    --cc=ajit.khaparde@broadcom.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=ke1.xu@intel.com \
    --cc=mingjinx.ye@intel.com \
    --cc=olivier.matz@6wind.com \
    --cc=qiming.yang@intel.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=stable@dpdk.org \
    --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).