netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: Aldo Maggi <sentiniate@tiscali.it>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>,
	Netdev <netdev@vger.kernel.org>
Subject: Re: tcp_sack problem Re: [Bug 11721] after upgrade to 2.6.27 i cannot navigate
Date: Mon, 20 Oct 2008 22:51:44 +0200	[thread overview]
Message-ID: <20081020205144.GA2837@ami.dom.local> (raw)
In-Reply-To: <20081020214818.09d88b48@topolino>

On Mon, Oct 20, 2008 at 09:48:18PM +0200, Aldo Maggi wrote:
...
> moreover, i read more carefully what you and Jarek wrote above, please let me
> know if you deem still necessary that i apply the patch you provided and
> compile or if you like i compile the latest kernel or whatever.

Aldo, my advice, in case Ilpo is busy now:

Since it looks like the problem/bug isn't in the kernel, but rather
somewhere in between (router, modem etc.) which is mislead by changed
(compared to 2.6.26) order of tcp options, I doubt Ilpo needs now
these dumps so much: it should be enough to say works or doesn't work.

You have checked it works in 2 cases (without tcp_sack, and without
tcp_timestamp) when mss is the first option again. With Ilpo's patch
these two options could be still present, and mss at the beginning.
It should work because it's like 2.6.26 did this, but I think, it
would be nice to check this anyway, if it's not a problem. Then
trying the latest kernel (at least 2.6.27) with this patch should be
most useful.

Thanks,
Jarek P.

  reply	other threads:[~2008-10-20 20:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11721-11547@http.bugzilla.kernel.org/>
     [not found] ` <20081018202056.F1933108040@picon.linux-foundation.org>
2008-10-18 21:02   ` tcp_sack problem Re: [Bug 11721] after upgrade to 2.6.27 i cannot navigate Jarek Poplawski
2008-10-18 21:50     ` Jarek Poplawski
2008-10-20  9:38       ` Jarek Poplawski
2008-10-20  9:38       ` Ilpo Järvinen
2008-10-20  9:51         ` Jarek Poplawski
2008-10-20  9:58           ` Ilpo Järvinen
2008-10-20 17:15             ` Jarek Poplawski
2008-10-20 19:48               ` Aldo Maggi
2008-10-20 20:51                 ` Jarek Poplawski [this message]
2008-10-20 20:55                 ` Ilpo Järvinen
     [not found]                   ` <20081020233419.78cd4390@topolino>
2008-10-20 21:51                     ` Ilpo Järvinen
2008-10-20 22:13                       ` Aldo Maggi
2008-10-21  5:26                       ` Aldo Maggi
     [not found]         ` <20081020225524.7a7c5d48@topolino>
2008-10-20 21:04           ` Ilpo Järvinen
     [not found] <20081020222914.GB2966@ami.dom.local>
     [not found] ` <20081021054903.GA4491@ff.dom.local>
     [not found]   ` <20081021092721.72ae73ea@topolino>
     [not found]     ` <20081021074954.GB4715@ff.dom.local>
     [not found]       ` <20081025221515.776a0a9b@topolino>
2008-10-22 11:49         ` two other cases " Aldo Maggi
2008-10-27  6:51           ` tcp_sack problem " Jarek Poplawski

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=20081020205144.GA2837@ami.dom.local \
    --to=jarkao2@gmail.com \
    --cc=ilpo.jarvinen@helsinki.fi \
    --cc=netdev@vger.kernel.org \
    --cc=sentiniate@tiscali.it \
    /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).