From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Joshua Washington <joshwash@google.com>,
Aman Singh <aman.deep.singh@intel.com>,
Yuying Zhang <yuying.zhang@intel.com>
Cc: dev@dpdk.org, Rushil Gupta <rushilg@google.com>
Subject: Re: [PATCH v6] app/testpmd: txonly multiflow port change support
Date: Fri, 19 May 2023 12:23:13 +0100 [thread overview]
Message-ID: <d9f4c2fa-2743-f200-ca7f-e964898a81a5@amd.com> (raw)
In-Reply-To: <20230519002249.2525777-1-joshwash@google.com>
On 5/19/2023 1:22 AM, Joshua Washington wrote:
> Google cloud routes traffic using IP addresses 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
> patch updates txonly multiflow mode to modify source ports instead of
> source IP addresses.
>
> The change can be tested with the following command:
> dpdk-testpmd -- --forward-mode=txonly --txonly-multi-flow \
> --tx-ip=<SRC>,<DST>
>
> Signed-off-by: Joshua Washington <joshwash@google.com>
> Reviewed-by: Rushil Gupta <rushilg@google.com>
>
Reviewed-by: Ferruh Yigit <ferruh.yigit@amd.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-05-19 11:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 20:17 [PATCH v2] " Joshua Washington
2023-04-11 20:24 ` [PATCH v3] " Joshua Washington
2023-04-12 18:16 ` [PATCH v4] " Joshua Washington
2023-04-19 12:21 ` Singh, Aman Deep
2023-04-19 14:38 ` Stephen Hemminger
2023-04-21 23:20 ` [PATCH v5] " Joshua Washington
2023-04-24 17:55 ` Joshua Washington
2023-04-25 6:56 ` David Marchand
2023-04-26 7:24 ` Singh, Aman Deep
2023-05-15 18:11 ` Joshua Washington
2023-05-15 22:26 ` Ferruh Yigit
2023-05-16 17:32 ` Joshua Washington
2023-05-17 10:10 ` Ferruh Yigit
2023-05-17 10:34 ` Ferruh Yigit
2023-05-19 0:22 ` [PATCH v6] " Joshua Washington
2023-05-19 11:23 ` Ferruh Yigit [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=d9f4c2fa-2743-f200-ca7f-e964898a81a5@amd.com \
--to=ferruh.yigit@amd.com \
--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).