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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 03 Feb 2016 11:23:46 -0800
From:	Eric Dumazet <>
To:	Alexander Duyck <>
Cc:	Hans Westgaard Ry <>,
	"David S. Miller" <>,
	Alexey Kuznetsov <>,
	James Morris <>,
	Hideaki YOSHIFUJI <>,
	Patrick McHardy <>,
	Tom Herbert <>,
	Pablo Neira Ayuso <>,
	Eric Dumazet <>,
	Florian Westphal <>, Jiri Pirko <>,
	Alexander Duyck <>,
	Michal Hocko <>,
	Linus Lüssing <>,
	Hannes Frederic Sowa <>,
	Herbert Xu <>,
	Tejun Heo <>,
	Andrew Morton <>,
	Alexey Kodanev <>,
	Håkon Bugge <>,
	open list <>,
	"open list:NETWORKING [GENERAL]" <>
Subject: Re: [PATCH v3] net:Add sysctl_max_skb_frags

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

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.

Powered by blists - more mailing lists