From: Baruch Even <baruch@ev-en.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Andrew Morton <akpm@osdl.org>,
shemminger@osdl.org, linux-kernel@vger.kernel.org,
netdev@oss.sgi.com
Subject: Re: 2.6.12-rc5-mm2: "bic unavailable using TCP reno" messages
Date: Thu, 02 Jun 2005 14:58:17 +0100 [thread overview]
Message-ID: <429F1079.5070701@ev-en.org> (raw)
In-Reply-To: <20050602121511.GE4992@stusta.de>
Adrian Bunk wrote:
> 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.
The best solution for this would be to check the available protocols at
setup time and not at connection creation time. This would also provide
a better feedback to the user, since he will either see that what he set
was taken, or it wasn't.
In the current mechanism you can set the protocol to 'foo' and it will
show back as 'foo'. You'll get complaints only once a connection is
attempted with this protocol.
It does mean some extra work in the sysctl stage, but it's better IMO to
do it there rather than at connection setup time.
Baruch
next prev parent reply other threads:[~2005-06-02 13:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20050601022824.33c8206e.akpm@osdl.org>
2005-06-02 12:15 ` 2.6.12-rc5-mm2: "bic unavailable using TCP reno" messages Adrian Bunk
2005-06-02 13:58 ` Baruch Even [this message]
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
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=429F1079.5070701@ev-en.org \
--to=baruch@ev-en.org \
--cc=akpm@osdl.org \
--cc=bunk@stusta.de \
--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 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).