From: "David S. Miller" <davem@davemloft.net>
To: shemminger@osdl.org
Cc: baruch@ev-en.org, netdev@oss.sgi.com, doug.leith@nuim.ie
Subject: Re: [RFC] TCP congestion infrastructure
Date: Mon, 09 May 2005 17:17:11 -0700 (PDT) [thread overview]
Message-ID: <20050509.171711.75189002.davem@davemloft.net> (raw)
In-Reply-To: <20050509162214.0a8c9ceb@dxpl.pdx.osdl.net>
From: Stephen Hemminger <shemminger@osdl.org>
Subject: [RFC] TCP congestion infrastructure
Date: Mon, 9 May 2005 16:22:14 -0700
> I rebased the H-TCP patches on my current work and 2.6.12-rc4 and put them in
> http://developer.osdl.org/shemminger/patches/2.6.12-rc4-tcp/
>
> Includes infrastructure and all the current variants: BIC, Westwood, Vegas
> plus H-TCP, Hybla
I like it. Looks fine from here.
This, along with the TSO reworking, will go in at the next
opportunity which is likely 2.6.13 of course.
I'm considering putting the TSO stuff into 2.6.12 because
in many ways it is a bug fix, TSO is fairly broken without
it. There are some loose ends I need to resolve first though.
next prev parent reply other threads:[~2005-05-10 0:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 17:37 [TCP 0/4] H-TCP patches on top of Stephens cc framework Baruch Even
2005-05-06 17:38 ` [PATCH TCP 1/4] Add undo callback to " Baruch Even
2005-05-06 17:39 ` [PATCH TCP 2/4] Implement H-TCP congestion control algorithm Baruch Even
2005-05-06 17:40 ` [PATCH TCP 3/4] Adjust alpha according to RTT timing Baruch Even
2005-05-06 17:41 ` [PATCH TCP 4/4] Switch out when bandwidth changes abruptly Baruch Even
2005-05-06 18:09 ` [TCP 0/4] H-TCP patches on top of Stephens cc framework Greg KH
2005-05-09 23:22 ` [RFC] TCP congestion infrastructure Stephen Hemminger
2005-05-10 0:17 ` David S. Miller [this message]
2005-05-10 16:13 ` Stephen Hemminger
2005-05-10 14:06 ` Baruch Even
2005-05-10 14:31 ` Baruch Even
2005-05-10 16:11 ` Stephen Hemminger
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=20050509.171711.75189002.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=baruch@ev-en.org \
--cc=doug.leith@nuim.ie \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.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).