From: Nageswara Rao <nagpen75@gmail.com>
To: stephen@networkplumber.org
Cc: dev@dpdk.org, ASHIQUE CK <ckashiquekvk@gmail.com>
Subject: Re: DPDK22 issue: Unable to set more than 4 queues in Azure
Date: Mon, 26 Jun 2023 15:53:12 +0530 [thread overview]
Message-ID: <CA+RWRMEps0Kv6RV9rZnd5CDwtQS3DCMbYrxi+0XXKLfFvkPaYQ@mail.gmail.com> (raw)
In-Reply-To: <20230625114829.7f49a9ff@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]
Yes, we are using vdev_netvsc. Native netvsc PMD we are observing issues in
enabling multiple queues.
Though we have 6 DPDK cores, unable to configure more than 4 queues.
On Mon, Jun 26, 2023 at 12:18 AM Stephen Hemminger <
stephen@networkplumber.org> wrote:
> On Thu, 22 Jun 2023 22:06:10 +0530
> Nageswara Rao <nagpen75@gmail.com> wrote:
>
> > Hi All,
> >
> > We are observing the following issue with DPDK22.11. We didn’t find any
> > upstream patches for this issue on the DPDK github. Is there any known
> > issue, please let us know.
> >
> >
> >
> > *Issue:*
> >
> > On Azure platform, we are unable to configure more than 4 queues. When we
> > try to configure more than 4 queues its failing with “EAL: Cannot send
> more
> > than 8 FDs” error.
> >
> > Here I am pasting the working and failing testpmd logs.
> >
> > Please note that this issue is not observed in DPDK 21.11.
> >
>
> You should be using the native netvsc PMD, not the
> vdev_netvsc,failsafe,tap kludge.
>
> I don't work on Azure any more but I suspect the issue is that the default
> in the kernel for TAP is for the number of queues == number of cores.
>
> You aren't going to see any real benefit from having more queues than
> the number of DPDK cores.
>
>
[-- Attachment #2: Type: text/html, Size: 1778 bytes --]
next prev parent reply other threads:[~2023-06-26 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 16:36 Nageswara Rao
2023-06-25 18:48 ` Stephen Hemminger
2023-06-26 10:23 ` Nageswara Rao [this message]
2023-06-26 16:25 ` Stephen Hemminger
2023-06-26 16:29 ` Nageswara Rao
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=CA+RWRMEps0Kv6RV9rZnd5CDwtQS3DCMbYrxi+0XXKLfFvkPaYQ@mail.gmail.com \
--to=nagpen75@gmail.com \
--cc=ckashiquekvk@gmail.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.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).