lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.00.0906231953480.2767@localhost.localdomain>
Date:	Tue, 23 Jun 2009 21:11:12 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	"Nikita V. Youshchenko" <yoush@...msu.su>
cc:	linux-kernel@...r.kernel.org,
	Alexander Kaliadin <akaliadin@...sta.com>
Subject: Re: [rt-preempt / powerpc] Looks like tick_sched_timer() is a major
 latency source

On Tue, 23 Jun 2009, Nikita V. Youshchenko wrote:
> 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.

> 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.

Thanks,

	tglx


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ