netdev - RE: Can I limit the number of active tx per TCP socket?

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1394204402.20149.29.camel@edumazet-glaptop2.roam.corp.google.com>
Date:	Fri, 07 Mar 2014 07:00:02 -0800
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	David Laight <David.Laight@...LAB.COM>
Cc:	'Neal Cardwell' <ncardwell@...gle.com>,
	Rick Jones <rick.jones2@...com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: Can I limit the number of active tx per TCP socket?

On Fri, 2014-03-07 at 14:35 +0000, David Laight wrote:

> Only the one connection between the two IP addresses is carrying this data.
> Other connections carry other traffic that has entirely different
> characteristics.

You can adapt the filter to match _this_ connection.

Other traffic will just use a different path (other qdisc if you prefer)

You can match things like source port, destination port, or fw marks
(using iptables or a socket option)

By letting the stack doing optimal aggregation, you'll have no overhead
an perfect pacing (using high resolution timer)

fq has the maxrate parameter so that you can avoid using
SO_MAX_PACING_RATE in the application.

By shaping the flow, you'll allow TCP stack to build efficient packets,
because tcp_sendmsg() will append data to the last skb in write queue,
thanks to auto corking.



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