All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Dâniel Fraga" <fragabr@gmail.com>
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 20:09:22 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0810052008131.3398@apollo> (raw)
In-Reply-To: <48e8fef7.0610c00a.5fa2.ffffaab0@mx.google.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2221 bytes --]

n Sun, 5 Oct 2008, Dâniel Fraga wrote:

> On Fri, 3 Oct 2008 00:19:08 +0300 (EEST)
> "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi> wrote:
> 
> > On Thu, 2 Oct 2008, Dâniel Fraga wrote:
> > 
> > > On Thu, 2 Oct 2008 23:31:28 +0300 (EEST)
> > > "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi> wrote:
> > > 
> > > > Ah, I was kind of thinking that you were doing something net related 
> > > > using some raw socket thing (such as traceroute) when you earlier 
> > > > mentioned sudo (iirc, we never really discussed what you usually do with 
> > > > it when you see the stall).
> > > 
> > > 	I read nntp groups everyday and I use leafnode. The stall on my
> > > desktop happens when I run fetchnews (which must be run as user "news"
> > > so I have to use sudo). Usually the stall on my desktop happens when
> > > I'm using fetchnews or some other command run by sudo.
> > 
> > Yes yes, I'd be specificly interested to have some rough idea what that
> > "some other command" includes, especially as some seem to be non-net 
> > related since you mentioned e.g., that /dev/log thing?
> 
> 	Here we go folks, good and bad news:
> 
> 1) the good news is that the Thomas' patch detected the stall, but...
> 
> 2)
> 
> Oct  5 14:23:03 teleporto vmunix: Tracer stopped
> Oct  5 14:23:13 teleporto last message repeated 2 times
> 
> 	if it had really stopped, the message wouldn't be repeated 2
> times.
> 
> 	and
> 
> fraga@teleporto ~$ cat /debug/tracing/tracing_enabled 
> 1
> 
> 	In other words, the tracing wasn't really stopped.
> 
> 	So I couldn't get what Thomas want. Should I activated the
> initial auto-checking of ftrace to see if it's really working? Very
> strange the fact it wasn't stopped.
> 
> 	***
> 
> 	I was waiting for 2 days to a stall and I managed to get the
> stall by using "sudo" multiple times. It seems that sudo really makes
> this bug hit.
> 	
> 	And now? Should we revise Thomas patch? Maybe a bug in ftrace
> code that prevents it from being stopped? It seems that:
> 
> ftrace_enabled = 0;
> 
> 	isn't really stopping the tracing.

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

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

Thanks,

	tglx

  reply	other threads:[~2008-10-05 18:09 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 [this message]
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=alpine.LFD.2.00.0810052008131.3398@apollo \
    --to=tglx@linutronix.de \
    --cc=davem@davemloft.net \
    --cc=fragabr@gmail.com \
    --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 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.