public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Revell <rlrevell@joe-job.com>
To: tglx@linutronix.de
Cc: "David S. Miller" <davem@davemloft.net>,
	Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] IPV4 long lasting timer function
Date: Thu, 18 Aug 2005 23:34:57 -0400	[thread overview]
Message-ID: <1124422498.25424.13.camel@mindpipe> (raw)
In-Reply-To: <1124312341.23647.277.camel@tglx.tec.linutronix.de>

On Wed, 2005-08-17 at 22:59 +0200, Thomas Gleixner wrote:
> Hi,
> 
> while tracking down some timer related ugliness I stumbled over the
> timer driven function rt_secret_rebuild(), which does a loop over
> rt_has_mask (1024 in my case) entries and possibly some subsequent
> variable sized loops inside each step.
> 
> On a 300MHZ PPC system this accumulated to a worst case total of >5ms. I
> could not reproduce it with this magnitude, but applying heavy
> networking load is definitely triggering this behaviour.
> 
> Shouldn't this be converted to a workqueue, which gets triggered by a
> timer instead of blocking the timer softirq and therefor the delivery of
> other timer functions that long ?

Wow, blast from the past!  This was one of the very first problematic
code paths Ingo and I identified in the early days of the voluntary
preempt patch (using the crude ALSA xrun debug mechanism which was the
best we had before /proc/latency_trace).

IIRC I was able to trivially reproduce it by leaving gtk-gnutella
running overnight with a few active searches/downloads.

Lee


      parent reply	other threads:[~2005-08-19  3:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-17 20:59 [RFC] IPV4 long lasting timer function Thomas Gleixner
2005-08-17 21:24 ` David S. Miller
2005-08-19  3:34 ` Lee Revell [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=1124422498.25424.13.camel@mindpipe \
    --to=rlrevell@joe-job.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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