DPDK usage discussions
 help / color / mirror / Atom feed
From: Nandini Rangaswamy <nandini.rangaswamy@broadcom.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Long Li <longli@microsoft.com>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: Netvsc vs Failsafe Performance
Date: Fri, 13 Sep 2024 10:56:10 -0700	[thread overview]
Message-ID: <CAAkQrK_HjT3H-xBtYdskrJ+oykf+djxOM41idg2w+7mW9EGytw@mail.gmail.com> (raw)
In-Reply-To: <20240912160948.3714f01d@hermes.local>

[-- Attachment #1: Type: text/plain, Size: 3058 bytes --]

Thanks for clarifying the question regarding Txd size Stephen.
I tested out the RSS for TCP UDP.
As suggested , I set the TCP flags alone in RSS conf and configured the
netvsc port.

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_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,
},
};
rte_eth_dev_configure(<netvsc port>, num_rxq,num_txq, &conf);
uint8_t rss_key_temp[64];
struct rte_eth_rss_conf rss_conf = {
.rss_key = rss_key_temp,
.rss_key_len = sizeof(rss_key_temp),
};
ret = rte_eth_dev_rss_hash_conf_get(<VF port>, &rss_conf);


Now the VF port RSS offloads show only TCP flags set and not UDP. I assumed
that even the UDP flags might be set. Is this expected ?

Regards,
Nandini


On Thu, Sep 12, 2024 at 4:09 PM Stephen Hemminger <
stephen@networkplumber.org> wrote:

> On Thu, 12 Sep 2024 13:47:37 -0700
> Nandini Rangaswamy <nandini.rangaswamy@broadcom.com> wrote:
>
> > Thanks for your response Long Li.
> > I see with netvsc the maximum number of Tx descriptors is restricted to
> > 4096 whereas the number of Rx descriptors is restricted to 8192.
> > But, for failsafe PMD , we see that both the number of Txd and Rxd is
> > restricted to 8192.
> > How is netvsc PMD giving the same performance as failsafe PMD ?
> >
> > Regards
>
> I think the limits there were somewhat arbitrary chose with netvsc.
> Don't remember a hard reason that would block larger sizes.
>
>
> Having really big rings won't help performance (i.e BufferBloat) and
> could a lot of memory consumption. When all heavy data traffic goes through
> the VF and that ring is different. Only DoS attacks should be impacted
> by rx/tx descriptor limits in the netvsc device. The linux driver actually
> has much smaller buffer.
>

-- 
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: 8929 bytes --]

  reply	other threads:[~2024-09-13 17:56 UTC|newest]

Thread overview: 15+ 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
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 [this message]
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-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_HjT3H-xBtYdskrJ+oykf+djxOM41idg2w+7mW9EGytw@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).