netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Baruch Even <baruch@ev-en.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@oss.sgi.com, Douglas Leith <doug.leith@nuim.ie>,
	"David S.Miller" <davem@davemloft.net>
Subject: Re: [RFC] TCP congestion infrastructure
Date: Tue, 10 May 2005 15:06:18 +0100	[thread overview]
Message-ID: <4280BFDA.3000909@ev-en.org> (raw)
In-Reply-To: <20050509162214.0a8c9ceb@dxpl.pdx.osdl.net>

Stephen Hemminger wrote:
> 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 compiled westwood and vegas as modules and got:

*** Warning: "tcpdiag_put" [net/ipv4/tcp_westwood.ko] undefined!
*** Warning: "tcpdiag_put" [net/ipv4/tcp_vegas.ko] undefined!

This is due to:

# CONFIG_IP_TCPDIAG is not set

in the .config.

Baruch

  parent reply	other threads:[~2005-05-10 14:06 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
2005-05-10 16:13     ` Stephen Hemminger
2005-05-10 14:06   ` Baruch Even [this message]
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=4280BFDA.3000909@ev-en.org \
    --to=baruch@ev-en.org \
    --cc=davem@davemloft.net \
    --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).