From: Arnd Bergmann <arnd@arndb.de>
To: Jiri Pirko <jiri@resnulli.us>
Cc: Jan Engelhardt <jengelh@inai.de>,
netdev@vger.kernel.org, ebiederm@xmission.com,
stephen@networkplumber.org, eric.dumazet@gmail.com,
davem@davemloft.net
Subject: Re: Universal tap device
Date: Sun, 17 Feb 2013 13:58:50 +0000 [thread overview]
Message-ID: <201302171358.50680.arnd@arndb.de> (raw)
In-Reply-To: <20130217093520.GA1931@minipsycho.orion>
On Sunday 17 February 2013, Jiri Pirko wrote:
>
> Sat, Feb 16, 2013 at 11:25:06PM CET, arnd@arndb.de wrote:
> >On Saturday 16 February 2013, Jiri Pirko wrote:
> >> Sat, Feb 16, 2013 at 05:46:25PM CET, jengelh@inai.de wrote:
> >> >On Saturday 2013-02-16 15:01, Jiri Pirko wrote:
> >> >
> >> >>Hi all.
> >> >>
> >> >>Looking at macvtap and thinking about the tap solutions in general,
> >> >>I think it would be handly to have some universal tap device.
> >> >
> >> >As in, allowing tuntap to register as an rx_handler for arbitrary
> >> >devices?
> >>
> >> Essentially yes, but I was thinking without the actual netdev:
> >> not eth0 -> tap0 -> chardev
> >> but eth0 -> chardev
> >>
> >> Not sure though if that is easily doable..
> >
> >Isn't that the same as setting up macvtap in PASSTHRU mode?
>
> Yep, but without netdev instance. That brings some issues. Maybe the
> netdev instance should be there. Not sure.
>
The idea of macvtap is at least that there should be no run-time
from using a separate netdev. Having the device is useful mostly
for configuration, especially with the non-passthrough modes
where you want to bind to a new mac address.
Arnd
next prev parent reply other threads:[~2013-02-17 13:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 14:01 Universal tap device Jiri Pirko
2013-02-16 16:46 ` Jan Engelhardt
2013-02-16 16:54 ` Jiri Pirko
2013-02-16 22:25 ` Arnd Bergmann
2013-02-17 9:35 ` Jiri Pirko
2013-02-17 13:58 ` Arnd Bergmann [this message]
2013-02-19 10:59 ` Jamal Hadi Salim
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=201302171358.50680.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=eric.dumazet@gmail.com \
--cc=jengelh@inai.de \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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