netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: bugme-daemon@bugzilla.kernel.org
Cc: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>, netdev@vger.kernel.org
Subject: tcp_sack problem Re: [Bug 11721] after upgrade to 2.6.27 i cannot navigate
Date: Sat, 18 Oct 2008 23:02:52 +0200	[thread overview]
Message-ID: <20081018210252.GA6048@ami.dom.local> (raw)
In-Reply-To: <20081018202056.F1933108040@picon.linux-foundation.org>

Nice job Aldo!

I forward this message to netdev and Cc our best tcp expert.
Any new replies should be rather "Reply All" (not bugzilla only).

Thanks,
Jarek P.

On Sat, Oct 18, 2008 at 01:20:56PM -0700, bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=11721
> 
...
> ------- Comment #30 from sentiniate@tiscali.it  2008-10-18 13:20 -------
> absolutely i'm not fed up! and actually i thank you for your patience.
> 
> i set paperino as you wrote and added ifconfig eth0 mtu 1400 as well
> i set the same value of mtu in topolino as well, i hope i was not wrong doing
> so!
> 
> i attach the files you ask for, but now i can navigate with 2.6.27-rc1-git1 as
> well!
> 
> afterwards i've run some more tests and have found out that the culprit is
> tcp_sack, if using kernel 2.6.27-rc1-gt1 it is set to "1" i cannot navigate if
> to "0" i can.
> so i enclose, should it be of any help, also the tcpdump on eth0 of topolino
> when on paperino tcp_sack is set to "1".
> 
> thanks
> aldo
> 
> 
> -- 
> Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.

       reply	other threads:[~2008-10-18 21:02 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   ` Jarek Poplawski [this message]
2008-10-18 21:50     ` tcp_sack problem Re: [Bug 11721] after upgrade to 2.6.27 i cannot navigate 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
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=20081018210252.GA6048@ami.dom.local \
    --to=jarkao2@gmail.com \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --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).