From: Yang Luan <luan.penny@gmail.com>
To: stephen@networkplumber.org
Cc: users@dpdk.org
Subject: Re: running DPDK application on Azure
Date: Wed, 13 Apr 2022 11:41:30 -0700 [thread overview]
Message-ID: <CAPHT=bYVN1+sKCsZ6tbbRwAtcGNbKoEX75t56dFr=BSQO-pi1w@mail.gmail.com> (raw)
In-Reply-To: <20220413085802.7506b1f8@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
Thanks Stephen.
Is the Netvsc PMD selected by default or I'll need to specify it somewhere?
Since I'm running a proprietary UDP protocol, 3rd parties (e.g. Azure)
won't know how a flow is established. I'm curious how exactly Azure selects
which NIC to receive a given packet?
Yang
On Wed, Apr 13, 2022 at 8:58 AM Stephen Hemminger <
stephen@networkplumber.org> wrote:
> On Tue, 12 Apr 2022 13:09:51 -0700
> Yang Luan <luan.penny@gmail.com> wrote:
>
> > Hi,
> >
> > We have an application using DPDK on AWS and would like to port it to
> > Azure. What would be recommended PMD to use? If I understand correctly,
> we
> > can either use the Netvsc PMD or the vdev_Netvsc PMD. It seems the Netvsc
> > PMD is newer.
>
> Short answer:
>
> Netvsc PMD is faster and can handle events better.
> vdev_netvsc/failsafe/tap is slower but can emulate some types of rte_flow.
>
> >
> > An alternative is to use the mlx4 PMD by only attaching to the mlx NIC's
> > PCI address. As I understand it, the concern is the mlx nic may not
> receive
> > all the packets. We run a proprietary UDP based protocol on top of DPDK.
> > Are all UDP packets guaranteed to be received by the mlx NIC?
>
> That won't work. the MLX device only sees established flows.
>
[-- Attachment #2: Type: text/html, Size: 1787 bytes --]
next prev parent reply other threads:[~2022-04-19 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 20:09 Yang Luan
2022-04-13 15:58 ` Stephen Hemminger
2022-04-13 18:41 ` Yang Luan [this message]
2022-04-13 23:36 ` 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='CAPHT=bYVN1+sKCsZ6tbbRwAtcGNbKoEX75t56dFr=BSQO-pi1w@mail.gmail.com' \
--to=luan.penny@gmail.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).