From: Stephen Hemminger <stephen@networkplumber.org>
To: Dattu Gundu <dattu.gundu@oracle.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [External] : Re: qdisc errors on Azure VM (TAP Config)
Date: Wed, 12 Oct 2022 10:11:01 -0700 [thread overview]
Message-ID: <20221012101101.42ad58b4@hermes.local> (raw)
In-Reply-To: <SA1PR10MB65173FA33718EEB680B0FDAA90229@SA1PR10MB6517.namprd10.prod.outlook.com>
On Wed, 12 Oct 2022 11:14:50 +0000
Dattu Gundu <dattu.gundu@oracle.com> wrote:
> Hi Stephen,
>
> Attached is the configuration params copied in the text file.
> Please let me know your pointers on the same.
Config looks like it should work.
Why are you not using the native netvsc PMD instead?
Failsafe/Tap/vdev_netvsc is excessively complex, and is slower.
next prev parent reply other threads:[~2022-10-12 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 6:08 Dattu Gundu
2022-10-06 16:31 ` Stephen Hemminger
2022-10-10 8:05 ` [External] : " Dattu Gundu
2022-10-10 14:56 ` Stephen Hemminger
2022-10-12 11:14 ` Dattu Gundu
2022-10-12 17:11 ` Stephen Hemminger [this message]
2022-10-17 9:13 ` Dattu Gundu
2022-10-17 15:01 ` 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=20221012101101.42ad58b4@hermes.local \
--to=stephen@networkplumber.org \
--cc=dattu.gundu@oracle.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).