netdev - Re: [PATCH v2 0/2] l2 hardware accelerated macvlans

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 05 Nov 2013 07:17:21 -0800
From:	John Fastabend <john.r.fastabend@...el.com>
To:	Vlad Yasevich <vyasevich@...il.com>
CC:	nhorman@...driver.com, alexander.h.duyck@...el.com,
	netdev@...r.kernel.org, andy@...yhouse.net, davem@...emloft.net,
	jeffrey.t.kirsher@...el.com
Subject: Re: [PATCH v2 0/2] l2 hardware accelerated macvlans

On 11/5/2013 6:47 AM, Vlad Yasevich wrote:
> Hi John
>

[...]

>> series. It would be best (I think) to use the software
>> path for macvlan to macvlan traffic and save the PCIe
>> bus. Also this only allows for layer 2 mac forwarding
>> where some hardware supports more interesting forwarding
>> capabilities. Integrating with OVS may be useful here.
>
> This seems to be saying that for macvlan-macvlan
> case, you still prefere to do software based forwarding, but
> patch 1 in the series seem to always attempt to do hardware
> offloaded forwarding regardless of traffic and macvlan type.
> Can you clarify.
>
> Thanks
> -vlad
>

This series always attempts to do hardware offload even in the
macvlan-macvlan case as you note. I'm suggesting a further
optimization might be to use the software based forwarding in
this case. My plan is to investigate this after I get the initial
series completed.

.John


--
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