public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: elko <elko@home.nl>
Cc: "José Luis Domingo López" <jdomingo@internautas.org>,
	linux-kernel@vger.kernel.org
Subject: Re: looking for a preempt-patch for 2.4.10-ac12
Date: 17 Oct 2001 15:53:54 -0400	[thread overview]
Message-ID: <1003348439.1575.3.camel@phantasy> (raw)
In-Reply-To: <01101721471803.00726@ElkOS>
In-Reply-To: <01101619524411.00955@ElkOS> <20011016204753.B1472@dardhal.mired.net>  <01101721471803.00726@ElkOS>

On Wed, 2001-10-17 at 15:47, elko wrote:
> the patch is there, I applied it together with the stats-patch
> and my system is running like a charm right now, never have seen
> this kind of response in X.

Glad everything is working smooth...

> the only thing is, the perl-script at:
> http://www.tech9.net/rml/linux/top-latencies
> 
> shows something this:
> 
> ----[ SNIP ]----
> n   min  avg  max  cause   mask start line/file address end line/file
>   14 9512 9590 9711  spin_lock 5 2111/tcp_ipv4.c c0226736119/softirq.c
>   89 9454 9559 9682  spin_lock 9 2111/tcp_ipv4.c c0226736119/softirq.c
>    2 9540 9551 9563  spin_lock 3 2111/tcp_ipv4.c c0226736119/softirq.c
> 3895 7708 9532 14296 spin_lock 1 2111/tcp_ipv4.c c0226736119/softirq.c
>    1 9513 9513 9513  spin_lock 1 2111/tcp_ipv4.c c02267362152/tcp_ipv4.c
>  363 3594 6166 9512  spin_lock 0 2111/tcp_ipv4.c c02267362152/tcp_ipv4.c
> ----[ SNIP ]----
> 
> that 3895 number for '2111/tcp_ipv4.c c0226736119/softirq.c'
> keeps adding up, how should I translate that? big network
> latency, is that what it means? if so, any idea on how
> can I fix that??

the n column is the number of times the lock has been held.  the lock is
probably held numerous times in a given second, so you see large n
values.

note that all those rows you showed could be in one row, but the
top-latencies tool keeps them separate since they have a different mask.

anyhow, the max recorded latency is 9.5ms which is not too bad.  I'm not
looking at the code, but I would imagine its some TCP work done in a
BH.  I wouldn't worry too much.

	Robert Love


      reply	other threads:[~2001-10-17 19:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-16 17:52 looking for a preempt-patch for 2.4.10-ac12 elko
2001-10-16 20:47 ` José Luis Domingo López
2001-10-17 19:47   ` elko
2001-10-17 19:53     ` Robert Love [this message]

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=1003348439.1575.3.camel@phantasy \
    --to=rml@tech9.net \
    --cc=elko@home.nl \
    --cc=jdomingo@internautas.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox