netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dâniel Fraga" <fragabr@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>,
	"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 17:46:37 -0300	[thread overview]
Message-ID: <48e3e1b1.0807c00a.62bc.2b32@mx.google.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0810012140360.5549@apollo.tec.linutronix.de>

On Wed, 1 Oct 2008 22:05:09 +0200 (CEST)
Thomas Gleixner <tglx@linutronix.de> wrote:

> Lots of things related to timers changed over the last kernel
> versions, but the big changes were 2.6.21 for 32bit and 2.6.24 for
> 64bit, where the high resolution timer were enabled. Since then we
> have only bigfixes and improvements in the timer related code. 2.6.25
> has no fundamental changes in the timer code at all.
> 
> I think your observation vs. ntpd and hrtimer is just a red
> herring. It influences the visibility of the problem by shifting
> timings around, but it does not pinpoint them as the root cause.
> 
> I might be wrong as usual, but in that case I insist on "in dubio pro
> reo". :)

	Ok :) I understand your point ;).

> One possibility to get deeper insight into this problem is to use the
> function tracer and stop it once we notice the wreckage. 
> listenoverflow should be a good point to stop it.

	Ok. I'll do it and return the results.

[*] Kernel Function Tracer

	Thank you very much! :)

	Ps: if we figure it out soon, maybe we can solve this before
2.6.27 final release since Linus said that rc8 would be the last one.

-- 

  reply	other threads:[~2008-10-01 20:46 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
2008-10-01 20:05   ` Thomas Gleixner
2008-10-01 20:46     ` Dâniel Fraga [this message]
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=48e3e1b1.0807c00a.62bc.2b32@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 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).