DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Joshua Washington <joshwash@google.com>
Cc: Aman Singh <aman.deep.singh@intel.com>,
	Yuying Zhang <yuying.zhang@intel.com>,
	dev@dpdk.org, Rushil Gupta <rushilg@google.com>
Subject: Re: [PATCH] app/testpmd: txonly multiflow port change support
Date: Tue, 11 Apr 2023 15:38:49 -0700	[thread overview]
Message-ID: <20230411153849.78615ebf@hermes.local> (raw)
In-Reply-To: <20230411201107.2798233-1-joshwash@google.com>

On Tue, 11 Apr 2023 13:11:07 -0700
Joshua Washington <joshwash@google.com> wrote:

> Google cloud routes traffic using IP addesses without the support of MAC
> addresses, so changing source IP address for txonly-multi-flow can have
> negative performance implications for net/gve when using testpmd. This
> change adds a new flag --txonly-alter-port, which allows the alteration
> of source port instead of source IP address for txonly multiflow mode.
> 
> The new flag can be tested with the following command:
> dpdk-testpmd -- --forward-mode=txonly --txonly-multi-flow --txonly-alter-port --txip=<SRC>,<DST>
> 
> Signed-off-by: Joshua Washington <joshwash@google.com>
> Reviewed-by: Rushil Gupta <rushilg@google.com>
> ---

Since the purpose of the tuple variation is to get RSS,
why not just make the udp port only mode the default.

Testpmd doesn't need more options :-)

      reply	other threads:[~2023-04-11 22:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11 20:11 Joshua Washington
2023-04-11 22:38 ` Stephen Hemminger [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=20230411153849.78615ebf@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=aman.deep.singh@intel.com \
    --cc=dev@dpdk.org \
    --cc=joshwash@google.com \
    --cc=rushilg@google.com \
    --cc=yuying.zhang@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).