From: Roopa Prabhu
Date: Tue, 31 Jan 2017 22:59:50 -0800
> lwt and dst_metadata have enabled vxlan l3 deployments
> to use a single vxlan netdev for multiple vnis eliminating the scalability
> problem with using a single vxlan netdev per vni. This series tries to
> do the same for vxlan netdevs i
On 2/2/17, 5:50 PM, David Miller wrote:
> I see a lot of "complexity of bridging layer" pushback on these
> changes, and I understand where that is coming from.
>
> But really this isn't even, at a high level, really a bridging change.
>
> What it's doing is making lwtunnel objects more useful.
>
>
I see a lot of "complexity of bridging layer" pushback on these
changes, and I understand where that is coming from.
But really this isn't even, at a high level, really a bridging change.
What it's doing is making lwtunnel objects more useful.
Now that we have lightweight tunnels and netdevs, w
On 2/1/17, 11:06 PM, Stephen Hemminger wrote:
> On Wed, 01 Feb 2017 21:58:25 -0800
> Roopa Prabhu wrote:
>
>> On 2/1/17, 5:23 PM, Alexei Starovoitov wrote:
>>> On Tue, Jan 31, 2017 at 10:59:50PM -0800, Roopa Prabhu wrote:
>>>
>>
[snip]
>>> I think most swith asics can do other tunnels too,
>>>
On Wed, 01 Feb 2017 21:58:25 -0800
Roopa Prabhu wrote:
> On 2/1/17, 5:23 PM, Alexei Starovoitov wrote:
> > On Tue, Jan 31, 2017 at 10:59:50PM -0800, Roopa Prabhu wrote:
> >
>
> [snip]
>
> >> Solution in this patch series:
> >> The Goal is to use a single vxlan device to carry all vnis similar
On 2/1/17, 5:23 PM, Alexei Starovoitov wrote:
> On Tue, Jan 31, 2017 at 10:59:50PM -0800, Roopa Prabhu wrote:
>
[snip]
>> Solution in this patch series:
>> The Goal is to use a single vxlan device to carry all vnis similar
>> to the vxlan collect metadata mode but additionally allowing the bridge
On 2/1/17, 8:04 PM, Stephen Hemminger wrote:
> On Wed, 01 Feb 2017 20:02:35 -0800
> Roopa Prabhu wrote:
>
>> On 2/1/17, 5:59 PM, David Ahern wrote:
>>> On 2/1/17 6:23 PM, Alexei Starovoitov wrote:
On Tue, Jan 31, 2017 at 10:59:50PM -0800, Roopa Prabhu wrote:
>
>>>
On Wed, 01 Feb 2017 20:02:35 -0800
Roopa Prabhu wrote:
> On 2/1/17, 5:59 PM, David Ahern wrote:
> > On 2/1/17 6:23 PM, Alexei Starovoitov wrote:
> >> On Tue, Jan 31, 2017 at 10:59:50PM -0800, Roopa Prabhu wrote:
> >>>
> >>> This provides the required vxlan bridging functi
On 2/1/17, 5:59 PM, David Ahern wrote:
> On 2/1/17 6:23 PM, Alexei Starovoitov wrote:
>> On Tue, Jan 31, 2017 at 10:59:50PM -0800, Roopa Prabhu wrote:
>>>
>>> This provides the required vxlan bridging function but poses a
>>> scalability problem with using a separate vxlan netd
On 2/1/17 6:23 PM, Alexei Starovoitov wrote:
> On Tue, Jan 31, 2017 at 10:59:50PM -0800, Roopa Prabhu wrote:
>>
>> This provides the required vxlan bridging function but poses a
>> scalability problem with using a separate vxlan netdev for each vni.
> if I remember correctly th
On Tue, Jan 31, 2017 at 10:59:50PM -0800, Roopa Prabhu wrote:
>
> This provides the required vxlan bridging function but poses a
> scalability problem with using a separate vxlan netdev for each vni.
if I remember correctly this issue was the main reason David Ahern
put netdev
From: Roopa Prabhu
High level summary:
lwt and dst_metadata have enabled vxlan l3 deployments
to use a single vxlan netdev for multiple vnis eliminating the scalability
problem with using a single vxlan netdev per vni. This series tries to
do the same for vxlan netdevs in pure l2 bridged networks
12 matches
Mail list logo
