From: Nandini Rangaswamy <nandini.rangaswamy@broadcom.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Long Li <longli@microsoft.com>, users@dpdk.org
Subject: Re: Netvsc vs Failsafe Performance
Date: Tue, 3 Sep 2024 17:21:48 -0700 [thread overview]
Message-ID: <CAAkQrK-gvVUsdyK+EiuaWZk9U7-CRZaJXHAELbV5qjMzmMv82A@mail.gmail.com> (raw)
In-Reply-To: <20240903170350.7e663864@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 2977 bytes --]
Hi Stephen/Long,
dpdk_netvsc_port_configure:1873 Configure port eth2/2. I am testing using
TCP traffic (iperf3 tool) generated between pair of client and servers with
DPDK app forward traffic between client and servers.
These are the config being passed for configuring netvsc:
lsc_intr=1
rxq/txq=2/2,
rss is enabled with rss_hf=0x0000000000000c30
tx_ol=0x00000000000006
rx_ol=0x00000000080007
Rsskey len is 64.
struct rte_eth_conf conf = {
.intr_conf = {
.lsc = !dpdk.lsc_intr_disable && !dpdk_if->lsc_intr_disable &&
!!(dev->data->dev_flags & RTE_ETH_DEV_INTR_LSC),
},
.rxmode = {
.mq_mode = RTE_ETH_MQ_RX_RSS,
.offloads = RTE_ETH_RX_OFFLOAD_VLAN_STRIP | RTE_ETH_RX_OFFLOAD_IPV4_CKSUM |
RTE_ETH_RX_OFFLOAD_RSS_HASH | RTE_ETH_RX_OFFLOAD_UDP_CKSUM,
},
.rx_adv_conf.rss_conf = {
.rss_hf = RTE_ETH_RSS_NONFRAG_IPV4_UDP | RTE_ETH_RSS_NONFRAG_IPV4_TCP |
RTE_ETH_RSS_NONFRAG_IPV6_TCP,
.rss_key = conf_rss_key,
.rss_key_len = rss_key_len,
},
.txmode = {
.offloads = RTE_ETH_TX_OFFLOAD_UDP_CKSUM | RTE_ETH_TX_OFFLOAD_IPV4_CKSUM,
},
Regards,
Nandini
On Tue, Sep 3, 2024 at 5:03 PM Stephen Hemminger <stephen@networkplumber.org>
wrote:
> On Tue, 3 Sep 2024 14:43:28 -0700
> Nandini Rangaswamy <nandini.rangaswamy@broadcom.com> wrote:
>
> > Hi Stephen and Long,
> > I was going through one of the netvsc patches
> > https://mails.dpdk.org/archives/dev/2018-August/110559.html which
> mentioned
> > that netvsc and failsafe give the same performance in VF path whereas for
> > some exception path tests, about 22% performance gain in seen.
> > I ran some tests locally with my dpdk app integrated with netvsc PMD and
> > observed that netvsc does give nearly the same performance as failsafe in
> > the VF path.
> > Since the official document does not explicitly cite this, I would like
> to
> > confirm if this holds good.
> > Regards,
> > Nandini
> >
>
> Shouldn't be. What settings are you using.
> Both failsafe and netvsc just pass packets to VF if present.
> There is even more locks to go through with failsafe.
>
> Are you sure the test doesn't exercise something like checksumming which
> maybe different.
>
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
[-- Attachment #2: Type: text/html, Size: 6812 bytes --]
next prev parent reply other threads:[~2024-09-04 0:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 21:43 Nandini Rangaswamy
2024-09-04 0:03 ` Stephen Hemminger
2024-09-04 0:21 ` Nandini Rangaswamy [this message]
2024-09-04 22:42 ` Stephen Hemminger
2024-09-05 2:30 ` Long Li
2024-09-12 20:47 ` Nandini Rangaswamy
2024-09-12 23:09 ` Stephen Hemminger
2024-09-13 17:56 ` Nandini Rangaswamy
2024-09-13 21:27 ` Long Li
2024-09-13 21:29 ` Nandini Rangaswamy
2024-09-16 22:58 ` Nandini Rangaswamy
2024-09-17 21:56 ` Long Li
2024-09-19 16:45 ` Nandini Rangaswamy
2024-10-16 19:26 ` Long Li
2024-10-17 18:32 ` Nandini Rangaswamy
2024-09-12 22:02 ` Nandini Rangaswamy
2024-09-12 22:59 ` Stephen Hemminger
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=CAAkQrK-gvVUsdyK+EiuaWZk9U7-CRZaJXHAELbV5qjMzmMv82A@mail.gmail.com \
--to=nandini.rangaswamy@broadcom.com \
--cc=longli@microsoft.com \
--cc=stephen@networkplumber.org \
--cc=users@dpdk.org \
/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).