From: Eric Dumazet <eric.dumazet@gmail.com>
To: Alexander Duyck <alexander.duyck@gmail.com>
Cc: "Hans Westgaard Ry" <hans.westgaard.ry@oracle.com>,
"David S. Miller" <davem@davemloft.net>,
"Alexey Kuznetsov" <kuznet@ms2.inr.ac.ru>,
"James Morris" <jmorris@namei.org>,
"Hideaki YOSHIFUJI" <yoshfuji@linux-ipv6.org>,
"Patrick McHardy" <kaber@trash.net>,
"Tom Herbert" <tom@herbertland.com>,
"Pablo Neira Ayuso" <pablo@netfilter.org>,
"Eric Dumazet" <edumazet@google.com>,
"Florian Westphal" <fw@strlen.de>,
"Jiri Pirko" <jiri@resnulli.us>,
"Alexander Duyck" <alexander.h.duyck@redhat.com>,
"Michal Hocko" <mhocko@suse.com>,
"Linus Lüssing" <linus.luessing@c0d3.blue>,
"Hannes Frederic Sowa" <hannes@stressinduktion.org>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Tejun Heo" <tj@kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Alexey Kodanev" <alexey.kodanev@oracle.com>,
"Håkon Bugge" <haakon.bugge@oracle.com>,
"open list" <linux-kernel@vger.kernel.org>,
"open list:NETWORKING [GENERAL]" <netdev@vger.kernel.org>
Subject: Re: [PATCH v3] net:Add sysctl_max_skb_frags
Date: Wed, 03 Feb 2016 11:23:46 -0800 [thread overview]
Message-ID: <1454527426.7627.282.camel@edumazet-glaptop2.roam.corp.google.com> (raw)
In-Reply-To: <CAKgT0UeueE5EhLu0-8jcr0+su81sOV_qCpb-KGRf7q4EKsw1QQ@mail.gmail.com>
On Wed, 2016-02-03 at 10:24 -0800, Alexander Duyck wrote:
> If this is only meant to be a performance modification and is only
> really targeted at TCP TSO/GRO then all I ask is that we use a name
> like tcp_max_gso_frags and relocate the sysctl to the TCP section.
> Otherwise if we are actually going to try to scope this out on a wider
> level and limit all frags which is what the name implies then the
> patch set needs to make a better attempt at covering all cases where
> it may apply.
This is the goal.
Other skb providers (like tun and af_packet) will also use this optional
limit.
I fail to see why Hans should send a complete patch series.
We will send followup patches, as we always did.
I will send the GRO change for example.
So please keep a sysctl name _without_ TCP in it, it really has nothing
to do with TCP.
next prev parent reply other threads:[~2016-02-03 19:23 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 13:16 [PATCH] net: add per device sg_max_frags for skb Hans Westgaard Ry
2016-01-06 13:59 ` David Laight
2016-01-08 9:55 ` Hans Westgaard Ry
2016-01-08 10:33 ` David Laight
2016-01-08 11:47 ` Hannes Frederic Sowa
2016-01-13 13:57 ` Hans Westgaard Ry
2016-01-13 14:19 ` Eric Dumazet
2016-01-13 14:20 ` Eric Dumazet
2016-01-13 15:07 ` Hannes Frederic Sowa
2016-01-13 15:38 ` David Miller
2016-01-13 15:44 ` Eric Dumazet
2016-01-13 21:07 ` Eric W. Biederman
2016-01-27 13:20 ` [PATCH v2] net:Add sysctl_tcp_sg_max_skb_frags Hans Westgaard Ry
2016-01-27 15:15 ` Eric Dumazet
2016-01-27 18:12 ` Hannes Frederic Sowa
2016-02-01 13:12 ` Hans Westgaard Ry
2016-01-27 20:13 ` David Miller
2016-02-03 8:26 ` [PATCH v3] net:Add sysctl_max_skb_frags Hans Westgaard Ry
2016-02-03 11:25 ` Herbert Xu
2016-02-03 11:36 ` Hannes Frederic Sowa
2016-02-03 12:20 ` Herbert Xu
2016-02-03 14:03 ` Hannes Frederic Sowa
2016-02-03 14:30 ` Eric Dumazet
2016-02-03 17:36 ` David Laight
2016-02-03 15:58 ` Alexander Duyck
2016-02-03 16:07 ` Eric Dumazet
2016-02-03 17:43 ` Alexander Duyck
2016-02-03 17:54 ` Eric Dumazet
2016-02-03 18:24 ` Alexander Duyck
2016-02-03 19:23 ` Eric Dumazet [this message]
2016-02-03 21:03 ` Alexander Duyck
2016-02-09 9:30 ` David Miller
2016-01-06 14:05 ` [PATCH] net: add per device sg_max_frags for skb Eric Dumazet
2016-01-08 10:01 ` Hans Westgaard Ry
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=1454527426.7627.282.camel@edumazet-glaptop2.roam.corp.google.com \
--to=eric.dumazet@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.duyck@gmail.com \
--cc=alexander.h.duyck@redhat.com \
--cc=alexey.kodanev@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=haakon.bugge@oracle.com \
--cc=hannes@stressinduktion.org \
--cc=hans.westgaard.ry@oracle.com \
--cc=herbert@gondor.apana.org.au \
--cc=jiri@resnulli.us \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linus.luessing@c0d3.blue \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.org \
--cc=tj@kernel.org \
--cc=tom@herbertland.com \
--cc=yoshfuji@linux-ipv6.org \
/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).