All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Christoph Lameter <cl@linux.com>, Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org
Subject: Re: Scheduler regression: Too frequent timer interrupts(?)
Date: Thu, 23 Apr 2009 06:42:29 +0200	[thread overview]
Message-ID: <20090423044228.GA2428@ucw.cz> (raw)
In-Reply-To: <1239982137.23397.4684.camel@laptop>

On Fri 2009-04-17 17:28:57, Peter Zijlstra wrote:
> On Fri, 2009-04-17 at 11:04 -0400, Christoph Lameter wrote:
> > On Fri, 17 Apr 2009, Peter Zijlstra wrote:
> > 
> > > And a random 1us cutoff, is well, random.
> > 
> > Its got to be somewhere.
> 
> No it doesn't, a cutoff is useless. If I steal cputime at units below
> the cutoff I can, in the limit, steal up to 100% cpu time and you'd not
> notice.

Are you sure cutoff is useless?

Irq entry/exit is sure to take > 1usec, right?

> > > So 5 <1us interruption are not at all accounted, whereas a single 1>us
> > > interruption is. I'd rather get rid of those 5 than try and shave a bit
> > > of the one, if you get what I mean.
> > 
> > Ok. We can set the threshold lower and see how that goes.
> 
> Pointless. See above.

I'd say that taking interrupt and returning in below 1000nsec is
impossible, even on very fast hw.

									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2009-04-25  8:16 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-16 19:53 Scheduler regression: Too frequent timer interrupts(?) Christoph Lameter
2009-04-17  7:00 ` Peter Zijlstra
2009-04-17 13:42   ` Christoph Lameter
2009-04-17 14:16     ` Peter Zijlstra
2009-04-17 14:29       ` Christoph Lameter
2009-04-17 14:51         ` Peter Zijlstra
2009-04-17 15:04           ` Christoph Lameter
2009-04-17 15:28             ` Peter Zijlstra
2009-04-23  4:42               ` Pavel Machek [this message]
2009-04-28 21:02                 ` Christoph Lameter
2009-04-28 21:23                   ` Peter Zijlstra
2009-04-28 21:21                     ` Christoph Lameter
2009-04-17 15:35             ` Ingo Molnar
2009-04-17 15:55               ` Christoph Lameter
2009-04-17 16:23                 ` Peter Zijlstra
2009-04-17 16:33                   ` Christoph Lameter
2009-04-17 16:49                   ` Ingo Molnar
2009-04-17 17:19                     ` Chris Friesen
2009-04-17 17:45                     ` Christoph Lameter
2009-04-17 18:11                       ` Peter Zijlstra
2009-04-17 18:20                         ` Christoph Lameter
2009-04-17 18:58                           ` Peter Zijlstra
2009-04-17 20:34                             ` Christoph Lameter
2009-04-17 20:53                               ` Peter Zijlstra
2009-04-17 23:24                           ` Chris Friesen
2009-04-18  7:35                             ` Ingo Molnar
2009-04-18  7:59                             ` Andi Kleen

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=20090423044228.GA2428@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=cl@linux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.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.