From: Jamal Hadi Salim <jhs@mojatatu.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, arnd@arndb.de, ebiederm@xmission.com,
stephen@networkplumber.org, eric.dumazet@gmail.com,
davem@davemloft.net
Subject: Re: Universal tap device
Date: Tue, 19 Feb 2013 05:59:41 -0500 [thread overview]
Message-ID: <51235B1D.1060109@mojatatu.com> (raw)
In-Reply-To: <20130216140132.GB1536@minipsycho.orion>
I dont know what macvtap is, but what dont you like about redirecting or
mirroring packets to tap? Or packet socket?
I think tap has become a christmas tree lately compared to its humble
beginnings, and its performance is questionable - but it should still
work for what you need.
cheers,
jamal
On 13-02-16 09:01 AM, 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.
>
> This could use rx_handler to hook onto any netdev and provide chardev
> tap-like iface to it. Using that, one can just hook onto macvlan device
> and macvtap would not be needed.
>
> This would allow other scenarios like vxlan-tap, vlan-tap, bond-tap or
> whatever.
>
> Does this idea seem to be reasonable?
>
> Thanks
>
> Jiri
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2013-02-19 10: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
2013-02-19 10:59 ` Jamal Hadi Salim [this message]
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=51235B1D.1060109@mojatatu.com \
--to=jhs@mojatatu.com \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=eric.dumazet@gmail.com \
--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 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.