From: Adrian Bunk <bunk@stusta.de>
To: Andrew Morton <akpm@osdl.org>, shemminger@osdl.org
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: 2.6.12-rc5-mm2: "bic unavailable using TCP reno" messages
Date: Thu, 2 Jun 2005 14:15:11 +0200 [thread overview]
Message-ID: <20050602121511.GE4992@stusta.de> (raw)
In-Reply-To: <20050601022824.33c8206e.akpm@osdl.org>
On Wed, Jun 01, 2005 at 02:28:24AM -0700, Andrew Morton wrote:
>...
> Changes since 2.6.12-rc5-mm1:
>...
> +tcp-tcp_infra.patch
>...
> Steve Hemminger's TCP enhancements.
>...
I said "no" to CONFIG_TCP_CONG_BIC, and now my syslog is full of messages
kernel: bic unavailable using TCP reno
I have no problem with such a message being shown once - but once should
be enough.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-06-02 12:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 9:28 2.6.12-rc5-mm2 Andrew Morton
2005-06-01 9:54 ` 2.6.12-rc5-mm2 Michal Schmidt
2005-06-01 12:22 ` 2.6.12-rc5-mm2 Stefano Rivoir
2005-06-01 21:53 ` 2.6.12-rc5-mm2 Dave Airlie
2005-06-01 14:02 ` 2.6.12-rc5-mm2 Pavel Machek
2005-06-01 15:04 ` 2.6.12-rc5-mm2 Matthias Urlichs
2005-06-03 10:12 ` 2.6.12-rc5-mm2 Pavel Machek
2005-06-05 19:20 ` 2.6.12-rc5-mm2 Matthias Urlichs
2005-06-01 16:48 ` 2.6.12-rc5-mm2 William Lee Irwin III
2005-06-01 23:47 ` 2.6.12-rc5-mm2 Matthew Dobson
2005-06-02 12:15 ` Adrian Bunk [this message]
2005-06-02 13:58 ` 2.6.12-rc5-mm2: "bic unavailable using TCP reno" messages Baruch Even
2005-06-02 17:38 ` Stephen Hemminger
2005-06-02 20:38 ` Adrian Bunk
2005-06-03 21:37 ` Stephen Hemminger
2005-06-03 22:32 ` Baruch Even
2005-06-02 20:07 ` [-mm patch] fix recursive IPW2200 dependencies Adrian Bunk
2005-06-02 20:19 ` Alejandro Bonilla
2005-06-02 20:54 ` 2.6.12-rc5-mm2 Adrian Bunk
2005-06-03 21:19 ` 2.6.12-rc5-mm2 Yani Ioannou
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=20050602121511.GE4992@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.