From: Baruch Even <baruch@ev-en.org>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: Adrian Bunk <bunk@stusta.de>, Andrew Morton <akpm@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: Fri, 03 Jun 2005 23:32:24 +0100 [thread overview]
Message-ID: <42A0DA78.2040804@ev-en.org> (raw)
In-Reply-To: <20050603143702.0422101d@dxpl.pdx.osdl.net>
Stephen Hemminger wrote:
> Here is what I am working on as better way to make the sysctl selection.
> I am not totally happy with the way the default congestion control value is determined
> by the load order. But it does seem good that if you load "tcp_xxx" module and it
> registers it becomes the default.
Looks good.
> @@ -120,6 +117,52 @@ static int ipv4_sysctl_forward_strategy(
> return 1;
> }
>
> +static int proc_tcp_congestion_control(ctl_table *ctl, int write, struct file * filp,
> + void __user *buffer, size_t *lenp, loff_t *ppos)
> +{
> + char val[TCP_CA_NAME_MAX];
> + ctl_table tbl = {
> + .data = val,
> + .maxlen = TCP_CA_NAME_MAX,
> + };
> + int ret;
> +
> + tcp_get_congestion_control(val);
Maybe we should call this tcp_get_current_congestion_control(), the
current name implies (to me) that you give it a name and it returns the
the ca struct. get_current might also just return the current one and
the strcpy can be done here.
Otherwise you probably should document the tcp_get_congestion_control()
to say what size of string it accepts.
Baruch
next prev parent reply other threads:[~2005-06-03 22:32 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
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 [this message]
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=42A0DA78.2040804@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).