From: Stephen Hemminger <stephen@networkplumber.org>
To: Solio Sarabia <solio.sarabia@intel.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
eric.dumazet@gmail.com, dsahern@gmail.com, kys@microsoft.com,
shiny.sebastian@intel.com,
Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [PATCH 2/2] veth: allow configuring GSO maximums
Date: Tue, 5 Dec 2017 17:25:10 -0800 [thread overview]
Message-ID: <20171205172510.1f3cfd9f@xeon-e3> (raw)
In-Reply-To: <1512522866-5544-3-git-send-email-solio.sarabia@intel.com>
On Tue, 5 Dec 2017 17:14:26 -0800
Solio Sarabia <solio.sarabia@intel.com> wrote:
> From: Stephen Hemminger <stephen@networkplumber.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@microsoft.com>
> Signed-off-by: Solio Sarabia <solio.sarabia@intel.com>
I am testing new version with changelink support
next prev parent reply other threads:[~2017-12-06 1:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 1:14 [PATCH 0/2] Allow changing device gso maximums Solio Sarabia
2017-12-06 1:14 ` [PATCH 1/2] rtnetlink: allow GSO maximums to be passed to device Solio Sarabia
2017-12-06 1:14 ` [PATCH 2/2] veth: allow configuring GSO maximums Solio Sarabia
2017-12-06 1:25 ` Stephen Hemminger [this message]
2017-12-06 1:50 ` Solio Sarabia
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=20171205172510.1f3cfd9f@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=kys@microsoft.com \
--cc=netdev@vger.kernel.org \
--cc=shiny.sebastian@intel.com \
--cc=solio.sarabia@intel.com \
--cc=sthemmin@microsoft.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).