linux-kernel - Re: Timing 250 versus 1000

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] [day] [month] [year] [list]

Date:	Sun, 08 Apr 2012 15:08:10 +0200
From:	Clemens Ladisch <clemens@...isch.de>
To:	Alex Stone <alex.parchment@...dex.ru>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Timing 250 versus 1000

Alex Stone wrote:
> Is there an important reason why timing in the kernel is set to 250 by default?

It's a compromise.  Read kernel/Kconfig.hz.

> those of us who write a lot of midi driven work, we're still more or
> less required to use some sort of RT kernel to get any degree of
> playback timing accuracy.

The ALSA sequencer timer stopped using the system timer years ago.
And the difference between RT and 'normal' kernels is not the timer
frequency.


Regards,
Clemens
--
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/