From: Anthony Liguori <anthony@codemonkey.ws>
To: Arnd Bergmann <arnd@arndb.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH, RFC] tap-linux: support opening arbitrary char devices
Date: Wed, 02 Dec 2009 09:46:18 -0600 [thread overview]
Message-ID: <4B168BCA.4010602@codemonkey.ws> (raw)
In-Reply-To: <200911262034.04440.arnd@arndb.de>
Arnd Bergmann wrote:
> With the upcoming macvtap, we will want to open devices other than
> /dev/net/tun but no longer need to call TUNSETIFF.
>
What are the names of these devices and how do you the character devices
get created in the first place?
This really isn't an "arbitrary" char device as it doesn't implement the
same interface as tap. Creation is done in a different manner.
> This makes it possible to do 'qemu -net tap,ifname=/dev/tap/macvtap0'
> to refer to a chardev in addition to the current way of doing
> 'qemu -net tap,ifname=tap0' to refer to a tap network interface
> set with TUNSETIFF. This is consistent with what we do on BSD.
>
We definitely don't want to overload ifname like this.
/dev/tap/macvtap0 is clearly not the interface name.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-12-02 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-26 19:34 [Qemu-devel] [PATCH, RFC] tap-linux: support opening arbitrary char devices Arnd Bergmann
2009-12-02 15:46 ` Anthony Liguori [this message]
2009-12-03 13:33 ` Arnd Bergmann
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=4B168BCA.4010602@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=arnd@arndb.de \
--cc=qemu-devel@nongnu.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).