From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 2A17C42D59; Mon, 26 Jun 2023 12:23:27 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 9F2B741149; Mon, 26 Jun 2023 12:23:26 +0200 (CEST) Received: from mail-pj1-f50.google.com (mail-pj1-f50.google.com [209.85.216.50]) by mails.dpdk.org (Postfix) with ESMTP id 935AB4067B for ; Mon, 26 Jun 2023 12:23:24 +0200 (CEST) Received: by mail-pj1-f50.google.com with SMTP id 98e67ed59e1d1-262e89a3ee2so508661a91.1 for ; Mon, 26 Jun 2023 03:23:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687775004; x=1690367004; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=WnlNyZNfmfDVsntCuqV/X4Zd2kBIQi/HZhX5Nn0sT0Q=; b=nH2fAwx20n8mu//5uoN4ERlHAGfqNGTuKHdlh6vKyqAGpCVP8Vymu1qoYV1P133cnr epITNKLenh5xdJT/o9RE03I8Y6HvmVM9AZMDOiVgW2y11pphiSZDjyQlZXKU0PNZ7uTK olqUmuxV8XvOxzb8DkOoZ3QC5aZMgzOQDm566inMz4DeBW+ZUjgh9TDWGJTN481yigvo hKmbEwRBNWzsKFjf8etf+f6KYnqGMAMsrYV9u+R+2qSN04oH2jBuLCroBsyPna8JlrPB Rhm+voHU/z5/2/ik35sY5erkJwAAp+sva0SI0txVuLspSi++VA3ks+1FC1ZP9R3YA06S VSwQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687775004; x=1690367004; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=WnlNyZNfmfDVsntCuqV/X4Zd2kBIQi/HZhX5Nn0sT0Q=; b=d/OGQD4fXNcF3tGc+1g88U/0ULND5eMMJmiK+W3HnTzjL9JlQIPpTB97vm8/07AdHm f4n8e16Czxiot5IqqvN5gL9LqgbTG0g9UbSUlYQHHLEqMM0Sw85acsb0YWEoUca9rDZ4 AeAfMu01sSUUUVG+WeDGR0dxYo7dzQS6zeowj9C92l5PmUhJ27PRxxKzFYU8Lumv2vw1 DRZdPucVIUdDes32F1cSK+UqAvJ/YHJElXua/zFiUtJiYskCKBYX31zpZxt1wbSCh1fE hg0jFYpzxWKgVqlQXqGdjgegfbcarMHYEXlFeeyl4Kc3Z4PmL3Kj43uIEXhsDiz53e2r JwHA== X-Gm-Message-State: AC+VfDy0rj+1QgDWsev0BU99v06kBzkPupqTVemo/FdjivfoPH9Lv5df z+D+Ay+qeSei+fonP7taTtHZgoylsfZzoFAIE9M= X-Google-Smtp-Source: ACHHUZ7FxGX4e+sBgN2+4s/tcIvPPHpoUflrwmwp3/eAWxAk8o6v5e2UQ37LoAWDjEwD7z2gj9Q9FMRJzoXZ7lZjcHs= X-Received: by 2002:a17:90a:35c:b0:263:6cb:5b95 with SMTP id 28-20020a17090a035c00b0026306cb5b95mr178231pjf.14.1687775003586; Mon, 26 Jun 2023 03:23:23 -0700 (PDT) MIME-Version: 1.0 References: <20230625114829.7f49a9ff@hermes.local> In-Reply-To: <20230625114829.7f49a9ff@hermes.local> From: Nageswara Rao Date: Mon, 26 Jun 2023 15:53:12 +0530 Message-ID: Subject: Re: DPDK22 issue: Unable to set more than 4 queues in Azure To: stephen@networkplumber.org Cc: dev@dpdk.org, ASHIQUE CK Content-Type: multipart/alternative; boundary="0000000000008cb36d05ff05bdb1" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --0000000000008cb36d05ff05bdb1 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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=E2=80=AFAM Stephen Hemminger < stephen@networkplumber.org> wrote: > On Thu, 22 Jun 2023 22:06:10 +0530 > Nageswara Rao wrote: > > > Hi All, > > > > We are observing the following issue with DPDK22.11. We didn=E2=80=99t = 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 =E2=80=9CEAL: Cann= ot send > more > > than 8 FDs=E2=80=9D 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 defaul= t > in the kernel for TAP is for the number of queues =3D=3D number of cores. > > You aren't going to see any real benefit from having more queues than > the number of DPDK cores. > > --0000000000008cb36d05ff05bdb1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Yes, we are using vdev_netvsc. Native netvsc PMD we are ob= serving issues in enabling multiple queues.=C2=A0
Though we have 6 DPDK= cores, unable to configure more than 4 queues.

On Mon, Jun 26, 2023= at 12:18=E2=80=AFAM Stephen Hemminger <stephen@networkplumber.org> wrote:
On Thu, 22 Jun 20= 23 22:06:10 +0530
Nageswara Rao <n= agpen75@gmail.com> wrote:

> Hi All,
>
> We are observing the following issue with DPDK22.11. We didn=E2=80=99t= 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 =E2=80=9CEAL: Can= not send more
> than 8 FDs=E2=80=9D 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 defa= ult
in the kernel for TAP is for the number of queues =3D=3D number of cores.
You aren't going to see any real benefit from having more queues than the number of DPDK cores.

--0000000000008cb36d05ff05bdb1--