From: David Miller <davem@davemloft.net>
To: rhee@eos.ncsu.edu
Cc: netdev@vger.kernel.org, shemminger@vyatta.com
Subject: Re: [PATCH] New Update on CUBIC
Date: Fri, 29 Feb 2008 10:46:33 -0800 (PST) [thread overview]
Message-ID: <20080229.104633.167255557.davem@davemloft.net> (raw)
In-Reply-To: <008401c87ad6$aea52e30$4a580e98@ncsu2cc0c3fa00>
From: "Injong Rhee" <rhee@eos.ncsu.edu>
Date: Fri, 29 Feb 2008 08:26:24 -0500
> @@ -211,19 +205,6 @@ static inline void bictcp_update(struct bictcp *ca, u32
> cwnd)
> ca->cnt = 100 * cwnd; /* very small increment*/
> }
>
> - if (ca->delay_min > 0) {
> - /* max increment = Smax * rtt / 0.1 */
> - min_cnt = (cwnd * HZ * 8)/(10 * max_increment * ca->delay_min);
> -
Please configure your email client to not corrupt the tabbing and to
also not break up long lines, as this makes the patch unusable.
Thank you.
prev parent reply other threads:[~2008-02-29 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 13:26 [PATCH] New Update on CUBIC Injong Rhee
2008-02-29 16:27 ` Stephen Hemminger
2008-02-29 18:46 ` David Miller [this message]
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=20080229.104633.167255557.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=rhee@eos.ncsu.edu \
--cc=shemminger@vyatta.com \
/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).