From: Stephen Hemminger <stephen@networkplumber.org>
To: Maxime Coquelin <maxime.coquelin@redhat.com>,
Tiwei Bie <tiwei.bie@intel.com>,
Zhihong Wang <zhihong.wang@intel.com>
Cc: dev@dpdk.org
Subject: [dpdk-dev] vtap0 device creation (bug)?
Date: Fri, 8 Nov 2019 15:44:07 -0800 [thread overview]
Message-ID: <20191108154407.0bd8734d@hermes.lan> (raw)
When I create a virtio-user device with rte_hotplug it creates a kernel device (ie vtap0).
This is normal an the device has ifindex N.
But later when device is configured an started the original vtap0 device is deleted
and a new one is created (with ifindex N+1). This seems like a bug, if nothing
else it unnecessary overhead and link flapping for routing daemons.
Noticed only while tracking down a bug where after vtap was created the
address was being set, but then disappearing.
Is this intentional? Is it documented?
next reply other threads:[~2019-11-08 23:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 23:44 Stephen Hemminger [this message]
2019-11-11 8:15 ` [dpdk-dev] vtap0 device creation (bug)? Tiwei Bie
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=20191108154407.0bd8734d@hermes.lan \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=tiwei.bie@intel.com \
--cc=zhihong.wang@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.