All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: davidwei79@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: A potential bug in tcp_vegas.c
Date: Thu, 08 Feb 2007 16:08:45 -0800 (PST)	[thread overview]
Message-ID: <20070208.160845.115912909.davem@davemloft.net> (raw)
In-Reply-To: <7335583a0702011303y5f3565d1r70a79eae94db6348@mail.gmail.com>


From: "Xiaoliang (David) Wei" <davidwei79@gmail.com>
Date: Thu, 1 Feb 2007 13:03:49 -0800

> I am testing tcp_vegas.c in Linux with the NS-2 TCP-Linux.
> It seems that the ssthresh is not correctly reset to 2 in the
> "tcp_vegas_cong_avoid" function.
> The problem might lead to very unfair behavior among Vegas flows, when
> some flows exit slow start due to loss, not delay.
> 
> Please see the detailed effect at:
> http://www.cs.caltech.edu/%7Eweixl/technical/ns2linux/known_linux/#vegas
> (the section of "Setting of Slow-Start-Threshold")
> 
> A patch I wrote (for Linux 2.6.19-2) is attached.
> Basically, the branch that sets ssthresh to be 2 should be outside the
> condition of (cwnd<=ssthresh).

Please provide a proper "Signed-off-by: " line, see
linux/Documentation/SubmittingPatches for details.

Your patch we not correctly rooted in the tree, the
diff file lines should use paths like:

--- a/net/ipv4/tcp_vegas.c.old     2007-02-01 00:33:55.000000000 -0800
+++ b/net/ipv4/tcp_vegas.c 2007-02-01 00:39:49.000000000 -0800

Again, see linux/Documentation/SubmittingPatches.

Also, GMAIL has corrupted your patch, turning all tab
characters into spaces, so that patch will not apply
properly.

If in doubt, try emailing the patch to yourself and
successfully applying it.

Please fix this up and resubmit, thank you.

  reply	other threads:[~2007-02-09  0:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-01 21:03 A potential bug in tcp_vegas.c Xiaoliang (David) Wei
2007-02-09  0:08 ` David Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-01  9:45 Xiaoliang (David) Wei

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=20070208.160845.115912909.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=davidwei79@gmail.com \
    --cc=netdev@vger.kernel.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.