All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Wu, Wenjun1" <wenjun1.wu@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"qiming.yang@intel.com--annotate"
	<qiming.yang@intel.com--annotate>
Cc: "Wu, Wenjun1" <wenjun1.wu@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/ice: remove redundant RSS configuration for GTPU
Date: Mon, 10 May 2021 02:59:50 +0000	[thread overview]
Message-ID: <232955b9c6ec4164b456ae5954412a73@intel.com> (raw)
In-Reply-To: <20210508084041.306170-1-wenjun1.wu@intel.com>



> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Wenjun Wu
> Sent: Saturday, May 8, 2021 4:41 PM
> To: dev@dpdk.org; qiming.yang@intel.com--annotate
> Cc: Wu, Wenjun1 <wenjun1.wu@intel.com>
> Subject: [dpdk-dev] [PATCH v2] net/ice: remove redundant RSS configuration for
> GTPU
> 
> Originally, the default RSS for GTPU is inner fields. Now, we hope outer RSS for
> GTPU to be the default.
> 
> Since RSS for ipv4, RSS for ipv6, RSS for UDP and RSS for TCP can cover the cases
> of outer RSS for GTPU, this patch deletes redundant default RSS configurations
> for GTPU.
> 
> Signed-off-by: Wenjun Wu <wenjun1.wu@intel.com>
> ---
> v2: GTPU and PPPoE share the value of cfg.hash_flds, patch v1 delete the
> assignment of cfg.hash_flds, which lead to RSS for PPPoE unable to work. Patch
> v2 adds these assignment statements.
> ---

Acked-by: Qi Zhang <qi.z.zhang@intel.com>

Applied to dpdk-next-net-intel.

Thanks
Qi


      reply	other threads:[~2021-05-10  2:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06  2:20 [dpdk-dev] [PATCH v1] net/ice: remove redundant RSS configuration for GTPU Wenjun Wu
2021-05-08  1:44 ` Zhang, Qi Z
2021-05-08  8:40 ` [dpdk-dev] [PATCH v2] " Wenjun Wu
2021-05-10  2:59   ` 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=232955b9c6ec4164b456ae5954412a73@intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=qiming.yang@intel.com--annotate \
    --cc=wenjun1.wu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.