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, 5 Dec 2017 17:25:10 -0800
From:   Stephen Hemminger <stephen@...workplumber.org>
To:     Solio Sarabia <solio.sarabia@...el.com>
Cc:     netdev@...r.kernel.org, davem@...emloft.net,
        eric.dumazet@...il.com, dsahern@...il.com, kys@...rosoft.com,
        shiny.sebastian@...el.com,
        Stephen Hemminger <sthemmin@...rosoft.com>
Subject: Re: [PATCH 2/2] veth: allow configuring GSO maximums

On Tue,  5 Dec 2017 17:14:26 -0800
Solio Sarabia <solio.sarabia@...el.com> wrote:

> From: Stephen Hemminger <stephen@...workplumber.org>
> 
> Veth's can be used in environments (like Azure) where the underlying
> network device is impacted by large GSO packets. This patch allows
> gso maximum values to be passed in when creating the device via
> netlink.
> 
> In theory, other pseudo devices could also use netlink attributes
> to set GSO maximums but for now veth is what has been observed
> to be an issue.
> 
> Signed-off-by: Stephen Hemminger <sthemmin@...rosoft.com>
> Signed-off-by: Solio Sarabia <solio.sarabia@...el.com>

I am testing new version with changelink support

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ