Re: [PATCH] tcp: Socket option to set congestion window

Andi Kleen
2010-05-27T08:00:27Z

On Wed, May 26, 2010 at 03:10:14PM -0700, David Miller wrote:
> From: Andi Kleen <andi@firstfloor.org>
> Date: Wed, 26 May 2010 23:27:45 +0200
>
> > As I understand the idea was that the application knows
> > what flows belong to a single peer and wants to have
> > a single cwnd for all of those. Perhaps there would
> > be a way to generalize that to tell it to the kernel.
> >
> > e.g. have a "peer id" that is known by applications
> > and the kernel could manage cwnds shared between connections
> > associated with the same peer id?
> >
> > Just an idea, I admit I haven't thought very deeply
> > about this. Feel free to poke holes into it.
>
> Yes, a CWND "domain" that can include multiple sockets is
> something that might gain some traction.
>
> The "domain" could just simply be the tuple {process,peer-IP}

If process is in there this wouldn't work for a multi process
server?

Perhaps having it associated with a FD so that it could
be passed around with unix sockets if needed (just would
need to make sure the AF_UNIX gc can handle such cycles)

peer_id = open_peer_id();
/* peer id is like a fd */

socket = socket( ... );
set_peer_id(socket, peer_id);

...

close(peer_id);

-andi
--
ak@linux.intel.com -- Speaking for myself only.