From: "Dâniel Fraga" <fragabr@gmail.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: tglx@linutronix.de, David Miller <davem@davemloft.net>,
Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] tcp FRTO: in-order-only "TCP proxy" fragility workaround (fwd)
Date: Wed, 1 Oct 2008 13:27:10 -0300 [thread overview]
Message-ID: <48e3a4e5.0d1d640a.4cd3.06e9@mx.google.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0810011546371.1034@wrl-59.cs.helsinki.fi>
On Wed, 1 Oct 2008 15:52:19 +0300 (EEST)
"Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi> wrote:
> Hi Daniel,
>
> I forward part of the details to public knowledge (and for Thomas mainly).
>
> I also put the epoll & accept only log available for him at
> http://www.cs.helsinki.fi/u/ijjarvin/tcp/epoll_accept.txt
> as it won't contain encryption key, etc. related bits.
>
> Can you Daniel please confirm what exactly was the status about the effect
> of disabling ntpd?
Hi Ilpo, ok, thanks. Following suggestion of kernel developers
from bugzilla, I tested with 2.6.27-rc7 and 2.6.27-rc8. The problem
happens less frequently, but still happens.
Disabling ntpd helps to not "trigger" the problem often. With
ntpd enabled the problem happens at least once a day. Without ntpd, it
doesn't happen anymore or seldom happens. Disabling high resolution
timers helps too.
I'll follow your previous suggestions, but I didn't have time
yet. If anyone needs more info, just ask. Thanks.
Ps: just to clarify for Thomas. The problem has started in
2.6.25 kernel and remain in 2.6.26 until now (2.6.27-rc8). Something
(probably related to timers) changed in 2.6.25 which causes this,
although the effect is seem on network stalling.
--
next prev parent reply other threads:[~2008-10-01 16:27 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 12:52 [PATCH] tcp FRTO: in-order-only "TCP proxy" fragility workaround (fwd) Ilpo Järvinen
2008-10-01 16:27 ` Dâniel Fraga [this message]
2008-10-01 20:05 ` Thomas Gleixner
2008-10-01 20:46 ` Dâniel Fraga
2008-10-01 21:14 ` Dâniel Fraga
2008-10-02 10:42 ` Thomas Gleixner
2008-10-02 11:17 ` Dâniel Fraga
2008-10-02 12:08 ` Thomas Gleixner
2008-10-02 14:09 ` Dâniel Fraga
2008-10-02 19:16 ` Thomas Gleixner
2008-10-02 20:31 ` Ilpo Järvinen
2008-10-02 20:59 ` Dâniel Fraga
2008-10-02 21:19 ` Ilpo Järvinen
2008-10-02 21:39 ` Dâniel Fraga
2008-10-05 17:52 ` Dâniel Fraga
2008-10-05 18:09 ` Thomas Gleixner
2008-10-05 19:31 ` Dâniel Fraga
2008-10-06 1:27 ` Dâniel Fraga
2008-10-08 19:34 ` Dâniel Fraga
2008-10-08 19:56 ` Thomas Gleixner
2008-10-08 20:44 ` Ilpo Järvinen
2008-10-10 4:20 ` Dâniel Fraga
2008-10-10 8:10 ` Thomas Gleixner
2008-10-11 8:27 ` Ilpo Järvinen
2008-10-11 13:38 ` Dâniel Fraga
2008-10-13 4:08 ` Dâniel Fraga
2008-10-13 13:35 ` Ilpo Järvinen
2008-10-13 18:32 ` Dâniel Fraga
2008-10-13 18:48 ` Nicolas Cannasse
2008-10-17 23:51 ` Dâniel Fraga
2008-10-20 21:48 ` Ilpo Järvinen
2008-10-20 21:49 ` Ilpo Järvinen
2008-10-22 2:12 ` Dâniel Fraga
2008-10-30 10:43 ` Ilpo Järvinen
2008-10-30 18:16 ` Dâniel Fraga
2008-11-02 5:56 ` [PATCH] tcp FRTO: in-order-only "TCP proxy" fragility workaround (fwd) [SOLVED] Dâniel Fraga
2008-11-03 15:37 ` Ilpo Järvinen
2008-11-03 17:03 ` Dâniel Fraga
2008-10-02 20:56 ` [PATCH] tcp FRTO: in-order-only "TCP proxy" fragility workaround (fwd) Dâniel Fraga
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=48e3a4e5.0d1d640a.4cd3.06e9@mx.google.com \
--to=fragabr@gmail.com \
--cc=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=netdev@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.