All of lore.kernel.org
 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: Sun, 5 Oct 2008 16:31:13 -0300	[thread overview]
Message-ID: <48e91606.0906c00a.2cd5.6a33@mx.google.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0810052008131.3398@apollo>

On Sun, 5 Oct 2008 20:09:22 +0200 (CEST)
Thomas Gleixner <tglx@linutronix.de> wrote:

> did you get the content of /debug/tracing/trace nevertheless ?

	Yes! I got several... maybe one is valid....

> The cat /debug/tracing/tracing_enabled == 1 might be just a user space
> interface thingy.

	Ok, here they are (I hope one of them is correct):

http://www.abusar.org/ftrace/

	These ones I get after I saw the kernel message "Tracer
stopped".

http://www.abusar.org/ftrace/trace.txt.bz2

http://www.abusar.org/ftrace/trace2.txt.bz2

http://www.abusar.org/ftrace/trace3.txt.bz2

http://www.abusar.org/ftrace/trace4.txt.bz2

http://www.abusar.org/ftrace/trace5.txt.bz2

	These ones were during a stall and after a nmap:

http://www.abusar.org/ftrace/trace-stop.txt.bz2

http://www.abusar.org/ftrace/trace-stop2.txt.bz2

	If none of these is valid, I will use monit to
check for Tracer stopped and force the tracing to be disabled.

-- 

  reply	other threads:[~2008-10-05 19:31 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
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 [this message]
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=48e91606.0906c00a.2cd5.6a33@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.