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 40283A0093 for ; Sat, 24 Dec 2022 12:16:17 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 13815410FB; Sat, 24 Dec 2022 12:16:17 +0100 (CET) Received: from mail-vs1-f50.google.com (mail-vs1-f50.google.com [209.85.217.50]) by mails.dpdk.org (Postfix) with ESMTP id 1C52B410E6 for ; Sat, 24 Dec 2022 12:16:15 +0100 (CET) Received: by mail-vs1-f50.google.com with SMTP id 3so6553922vsq.7 for ; Sat, 24 Dec 2022 03:16:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=L0H1PnzeEWM6NospCroj1AQkqB+osHe5rAK3eD/64PU=; b=OZKQMhLLSNGxf/IF/J3ltP2jwr1C98RgR/sX9feRmATlkEP9W46Bt6Y6UwwAYM3y8K LpW8ZG0NUuuYDQaAW1zHjkrFoWQJyTVOh8R32IPGnfHkHcGNzN8PyIkvDKGEV5luRhtI W7LvnYTVXTrMwFEnSnqerZv2/kaqVCr6jqAoeQ1b149zjW9rL3fahHWtWvexhqiuUXll VRvkGbZypwInngaQ1pQISPK2xiWSSnS0B4/ocaIFBa9BEu2cWfjhESHst5Ca+CE51vyk bXzgnh1x0nYIUr430jfwVwQNXERiMlbk5sdSSy8XrM8GjAn4yUOxJnswX3gQ/JnAS5X2 YHsA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=L0H1PnzeEWM6NospCroj1AQkqB+osHe5rAK3eD/64PU=; b=x7aG3Ct9PEJLcpVutuglwPyDbUh5Y76oDeMwyqgSd7QdGWPaofxpW8KXR4Lh31aVrv fPifRuk3Go9GFavd4goQgZqACjV2okKyRiqwwTwMc9ulCeTdFqmZovYXmUYLp6G37ARB gHzjZJ1ir969B7LqW0QTAluT3WEzsvmyxDRWc8tbLcklMGT9NXIlQgF6t8Dn5ZP6g3q5 Vc/Yops0N7tgThXbvjMwv9bAFFcKMgznopGeAMRWfV/NWGNmJmJ827fn7P2N6y6PTFqI U4E9VBhf4gm/EHMUdQhAN1/xmqi0i0O7HOOzimgdl0BxRlHBMzoZ3XclXQvuGwqTbGXL WUiA== X-Gm-Message-State: AFqh2kohfMjcDMdmFdrgIPAzBZxvVX+LQenCuz1Fs/ghPy7vOV1LI+K2 bLC+7NRQzc0dfDWSyJcPO6rTmJa/DHh2iRhkP7w= X-Google-Smtp-Source: AMrXdXu+FsoYKFjIxYNMWO7eKpknbPnT/8lZQ1T+yecrCnyVlC4jGOzOEld6F1Z5I2ReNGbyAtuH+4lKGGb5EpM6XUQ= X-Received: by 2002:a67:fdd7:0:b0:3b1:2ff7:543b with SMTP id l23-20020a67fdd7000000b003b12ff7543bmr1427758vsq.66.1671880574435; Sat, 24 Dec 2022 03:16:14 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a05:612c:270a:b0:303:2091:c35c with HTTP; Sat, 24 Dec 2022 03:16:13 -0800 (PST) In-Reply-To: References: From: Hui Ling Date: Sat, 24 Dec 2022 19:16:13 +0800 Message-ID: Subject: Re: Performance issues while using DPDK with azure accelerated networking To: piyush gupta Cc: "users@dpdk.org" Content-Type: multipart/alternative; boundary="000000000000bf09ec05f0910720" X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org --000000000000bf09ec05f0910720 Content-Type: text/plain; charset="UTF-8" vdev_netvsc is not what you are looking for. This is what you need. http://doc.dpdk.org/guides-22.11/nics/netvsc.html On Friday, December 23, 2022, piyush gupta wrote: > Hi, > > I am running a D8sV3 type instance on azure with RHEL7.9 & accelerated networking enabled on one of the interface. > > On this am running my DPDK app which is binding to the VF exposed & its corresponding netvsc interface via vdev_netvsc driver as suggested in https://learn.microsoft.com/en-us/azure/virtual-network/setup-dpdk > > DPDK doc : vdev_netvsc.html > > The expected behaviour is that all traffic should flow through the physical interface (VF) and not from synthetic device (eth2 in my case). > But I can see all traffic coming to eth2 & dtap0 devices. This is causing my dpdk cpus to handle RX interrupts for these packets causing major performance issues & jitters. I am not understanding why all these packets are being mirrored to slow path. > > Note: All my traffic is UDP. > > > > > > > I would like to know if there is any setting I am missing here. This is causing a lot of problems for me to qualify on Azure cloud with expected throughput. > > Thanks. > > Best regards, > > Piyush Gupta > > --000000000000bf09ec05f0910720 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable vdev_netvsc is not what you are looking for.

This is what you need.<= br>
http:/= /doc.dpdk.org/guides-22.11/nics/netvsc.html


On Friday, Decem= ber 23, 2022, piyush gupta <pgup= ta9393@gmail.com> wrote:
> Hi,
>
> I am running a= =C2=A0D8sV3=C2=A0type instance on azure with=C2=A0RHEL7.9=C2=A0& accele= rated networking enabled on one of the interface.
>
> On this a= m running my DPDK app which is binding to the VF exposed & its correspo= nding netvsc interface via=C2=A0vdev_netvsc driver=C2=A0as suggested in=C2= =A0https://learn.microsoft.com/en-us/azure/virtual-network/setup-dpdk
>
> DPDK doc :=C2=A0vdev_netvsc.html
>
> The exp= ected behaviour is that all traffic should flow through the physical interf= ace (VF) and not from synthetic device (eth2 in my case).
> But I can= see all traffic coming to eth2 & dtap0 devices. This is causing my dpd= k cpus to handle RX interrupts for these packets causing major performance = issues & jitters. I am not understanding why all these packets are bein= g mirrored to slow path.
>
> Note: All my traffic is UDP.
&g= t;
> =C2=A0
>
> </mail/u/0/s/?view=3Datt&th=3D1854= 395b0da9d888&attid=3D0.1&disp=3Demb&realattid=3Dii_lc04zfx20&am= p;zw&atsh=3D1>
> </mail/u/0/s/?view=3Datt&th=3D1854395b= 0da9d888&attid=3D0.2&disp=3Demb&realattid=3Dii_lc04zfxt1&zw= &atsh=3D1>
>
> I would like to know if there is any sett= ing I am missing here. This is causing a lot of problems for me to qualify = on Azure cloud with expected throughput.
>
> Thanks.
>> Best regards,
>
> Piyush Gupta
>
> =C2=A0 --000000000000bf09ec05f0910720--