All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jarek Poplawski <jarkao2@gmail.com>
To: =?ISO-8859-1?Q?Ilpo_J=E4rvinen?= <ilpo.jarvinen@helsinki.fi>
Cc: Aldo Maggi <sentiniate@tiscali.it>,
	Netdev <netdev@vger.kernel.org>,
	bugme-daemon@bugzilla.kernel.org
Subject: Re: tcp_sack problem Re: [Bug 11721] after upgrade to 2.6.27 i cannot navigate
Date: Mon, 20 Oct 2008 19:15:30 +0200	[thread overview]
Message-ID: <20081020171530.GA2564@ami.dom.local> (raw)
In-Reply-To: <Pine.LNX.4.64.0810201256120.7072@wrl-59.cs.helsinki.fi>

On Mon, Oct 20, 2008 at 08:47:37AM -0700, bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=11721
...
> ------- Comment #40 from sentiniate@tiscali.it  2008-10-20 08:47 -------
> ok setting echo 0 > /proc/sys/net/ipv4/tcp_timestamps solves the problem as
> well.
> 
> anyway i'm willing to do whatever test you deem necessary if this can help you
> solve the issue, so as soon as i can i'll apply the patch provided by  Ilpo
> Järvinen and compile (do not worry i've been a linux user for the last 10
> years and up to 4 or 5 yrs ago i used to compile even three times a week!)
> 
> thanks
> aldo

Aldo, I forward this message to Ilpo and netdev, because "they" aren't
on the Cc list of this report. (With next replies try to use the mail
with their addresses.)

I think, you could test Ilpo's patch as well: this would make slightly
different test/header. (Of course, all these /proc tcp values and mtus
should be back to normal.)

Thanks,
Jarek P.

  reply	other threads:[~2008-10-20 17:15 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 [this message]
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=20081020171530.GA2564@ami.dom.local \
    --to=jarkao2@gmail.com \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --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 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.