From: Hui Ling <kelvin.brookletling@gmail.com>
To: piyush gupta <pgupta9393@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: Performance issues while using DPDK with azure accelerated networking
Date: Sat, 24 Dec 2022 19:16:13 +0800 [thread overview]
Message-ID: <CAPNMKd5d3zBbP7eSYZAy_A+A0Vtk9Lpd77aRn_e=J2SjCpNqSg@mail.gmail.com> (raw)
In-Reply-To: <CANSLT0aKvoNB0EX6c_0Feh1TcM_SoUBj6hgzytgoFt=OWBa6aw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1409 bytes --]
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 <pgupta9393@gmail.com> 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.
>
>
>
>
</mail/u/0/s/?view=att&th=1854395b0da9d888&attid=0.1&disp=emb&realattid=ii_lc04zfx20&zw&atsh=1>
>
</mail/u/0/s/?view=att&th=1854395b0da9d888&attid=0.2&disp=emb&realattid=ii_lc04zfxt1&zw&atsh=1>
>
> 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
>
>
[-- Attachment #2: Type: text/html, Size: 1876 bytes --]
prev parent reply other threads:[~2022-12-24 11:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 6:37 piyush gupta
2022-12-24 11:16 ` Hui Ling [this message]
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='CAPNMKd5d3zBbP7eSYZAy_A+A0Vtk9Lpd77aRn_e=J2SjCpNqSg@mail.gmail.com' \
--to=kelvin.brookletling@gmail.com \
--cc=pgupta9393@gmail.com \
--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).