mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Nikita V. Youshchenko" <yoush@cs.msu.su>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, Alexander Kaliadin <akaliadin@mvista.com>
Subject: Re: [rt-preempt / powerpc] Looks like tick_sched_timer() is a major latency source
Date: Wed, 24 Jun 2009 00:01:47 +0400	[thread overview]
Message-ID: <200906240001.48924@blacky.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.00.0906231953480.2767@localhost.localdomain>

> > I tried hard to identify the latency source, and at some moment
> > discovered tick_sched_timer() from kernel/time/tick-sched.c. This
> > routine is called from timer interrupt with hardware interrupts
> > disabled, and may execute for 50 us and more.
> >
> > Could someone please comment on this?
>
> Did you have CONFIG_NOHZ enabled ? If yes, please disable.

I have disabled CONFIG_NOHZ long ago, since it really influences latency.

> > Is it possible to move (part of) tick_sched_timer() call tree out of
> > hardware-interrupts-disabled context without breaking things?
>
> Yes, we can move things out and split the irq disabled regions. One
> particular thing which can be split out is the time update, which we
> already had in the timer softirq at some point, but we moved it back
> as it showed problems with NTP stability. It's one of the things which
> can be revisited. The whole call chain needs some investigation, but
> that's not in my main focus now.

Is that code with time update split out available anywhere?

Nikita

      reply	other threads:[~2009-06-23 20:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23 16:55 Nikita V. Youshchenko
2009-06-23 19:11 ` Thomas Gleixner
2009-06-23 20:01   ` Nikita V. Youshchenko [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=200906240001.48924@blacky.localdomain \
    --to=yoush@cs.msu.su \
    --cc=akaliadin@mvista.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®