netdev - Re: [PATCH net-next v2 1/2] openvswitch: Use regular GRE net

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20150804060140.GA47336@Alexeis-MBP.westell.com>
Date:	Mon, 3 Aug 2015 23:01:41 -0700
From:	Alexei Starovoitov <alexei.starovoitov@...il.com>
To:	Pravin Shelar <pshelar@...ira.com>
Cc:	David Miller <davem@...emloft.net>, netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next v2 1/2] openvswitch: Use regular GRE net_device
 instead of vport

On Mon, Aug 03, 2015 at 10:58:02PM -0700, Pravin Shelar wrote:
> >> > feature detection based on netdev name?
> >> > meaning that there will be only one such device for the whole
> >> > host? and namespaces cannot have their own gre tunnels?
> >> > (since host 'gretap0' cannot be seen in netns)
> >> >
> >> gretap0 exist in every namespace. This device is created in GRE namespce init.
> >
> > then all of them get to be in flow_based mode without being able to
> > change it?
> >
> Yes, But there is no side effect of this feature for the user of the device.

other than allocating metadata_dst for every incoming packet?
If you could actually do it for free then we wouldn't need a flag.

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html