Re: [PATCH net-next 2/2] tcp: add TCP_CC_INFO socket option

2015-04-29 Thread David Miller
From: Eric Dumazet Date: Tue, 28 Apr 2015 16:23:49 -0700 > Some Congestion Control modules can provide per flow information, > but current way to get this information is to use netlink. > > Like TCP_INFO, let's add TCP_CC_INFO so that applications can > issue a getsockopt() if they have a socket

Re: [PATCH net-next 2/2] tcp: add TCP_CC_INFO socket option

2015-04-29 Thread Daniel Borkmann
On 04/29/2015 01:07 PM, Eric Dumazet wrote: On Wed, 2015-04-29 at 10:17 +0200, Daniel Borkmann wrote: On 04/29/2015 01:23 AM, Eric Dumazet wrote: Some Congestion Control modules can provide per flow information, but current way to get this information is to use netlink. Like TCP_INFO, let's ad

Re: [PATCH net-next 2/2] tcp: add TCP_CC_INFO socket option

2015-04-29 Thread Daniel Borkmann
On 04/29/2015 01:23 AM, Eric Dumazet wrote: Some Congestion Control modules can provide per flow information, but current way to get this information is to use netlink. Like TCP_INFO, let's add TCP_CC_INFO so that applications can issue a getsockopt() if they have a socket file descriptor, inste

Re: [PATCH net-next 2/2] tcp: add TCP_CC_INFO socket option

2015-04-28 Thread Neal Cardwell
On Tue, Apr 28, 2015 at 7:23 PM, Eric Dumazet wrote: > Some Congestion Control modules can provide per flow information, > but current way to get this information is to use netlink. > > Like TCP_INFO, let's add TCP_CC_INFO so that applications can > issue a getsockopt() if they have a socket file

[PATCH net-next 2/2] tcp: add TCP_CC_INFO socket option

2015-04-28 Thread Eric Dumazet
Some Congestion Control modules can provide per flow information, but current way to get this information is to use netlink. Like TCP_INFO, let's add TCP_CC_INFO so that applications can issue a getsockopt() if they have a socket file descriptor, instead of playing complex netlink games. Sample u