From: "Damon L. Chesser" <damon@damtek.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: Bug 213081 <213081@bugs.launchpad.net>,
478062@bugs.debian.org, Netdev <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>
Subject: Re: Fix FRTO+NewReno problem (Was: Re: This has a work around)
Date: Thu, 08 May 2008 13:05:38 -0400 [thread overview]
Message-ID: <482332E2.6080104@damtek.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0805072357240.23091@wrl-59.cs.helsinki.fi>
Ilpo Järvinen wrote:
Snip
>
> Could you next try with tcp_frto set to 1, if my theory proves to be
> correct, it too should be "enough" to fix the problem (in this
> particular case). Of course you can verify the patch below too if you
> want to, the patch should allow cups<->printer to work with tcp_frto =
> 2 too. In case you have problem to apply the patch to the particular
> version you're want to try with, just send a note about the version
> number to me so I can adapt the patch for you (space etc. formatting
> issues may show up because I recently run a code style cleanup on the
> tcp code).
>
Ilpo,
and all others, please ignore frtoprob1.txt. I ran the test on the
wrong kernel. The tested kernel was 2.6.23.17-amd64 and should have
been 2.6.24-1-amd64. I am re-running the test and will forward the new
dump. No idea why 2.6.23.17 did not print, it always did before. I am
sure I did something stupid, feeling a bit under the weather. Sorry for
the confusion. New test comming shortly.
--
Damon L. Chesser
damon@damtek.com
http://www.linkedin.com/in/dchesser
next prev parent reply other threads:[~2008-05-08 17:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48207F06.50306@damtek.com>
[not found] ` <Pine.LNX.4.64.0805061912350.8965@wrl-59.cs.helsinki.fi>
[not found] ` <4821C37A.7040306@damtek.com>
2008-05-07 22:26 ` Fix FRTO+NewReno problem (Was: Re: This has a work around) Ilpo Järvinen
2008-05-08 8:10 ` Fix FRTO+NewReno problem David Miller
2008-05-08 16:50 ` Bug#478062: Fix FRTO+NewReno problem (Was: Re: This has a work around) Damon L. Chesser
2008-05-08 17:05 ` Damon L. Chesser [this message]
2008-05-08 18:16 ` Damon L. Chesser
2008-05-08 20:42 ` Ilpo Järvinen
2008-05-12 10:08 ` Ilpo Järvinen
[not found] ` <4828279C.3010102@damtek.com>
2008-05-12 11:32 ` Ilpo Järvinen
2008-05-12 11:55 ` Damon L. Chesser
2008-05-12 12:07 ` Ilpo Järvinen
2008-05-12 13:44 ` Damon L. Chesser
2008-05-12 14:35 ` Ilpo Järvinen
2008-05-12 16:40 ` Ilpo Järvinen
2008-05-12 17:02 ` Damon L. Chesser
2008-05-12 18:23 ` Ilpo Järvinen
2008-05-12 18:39 ` Damon L. Chesser
2008-05-12 19:12 ` Ilpo Järvinen
2008-05-12 19:18 ` Damon L. Chesser
2008-05-12 19:25 ` Ilpo Järvinen
2008-05-12 22:48 ` Fix FRTO+NewReno problem David Miller
2008-05-13 9:42 ` Ilpo Järvinen
2008-05-13 9:49 ` David Miller
2008-05-13 10:04 ` Ilpo Järvinen
2008-05-13 10:08 ` David Miller
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=482332E2.6080104@damtek.com \
--to=damon@damtek.com \
--cc=213081@bugs.launchpad.net \
--cc=478062@bugs.debian.org \
--cc=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--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 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).