Bug#311185: linux-2.6: Does the Debian Kernel Team still have concerns about CONFIG_PREEMPT ?
Package: linux-2.6
Followup-For: Bug #311185
If I understand the following output correctly, the current (testing) Linux
kernel does *not* have any preemption activated:
$ grep -i EMPT /boot/config-2.6.22-3-amd64
CONFIG_PREEMPT_NONE=y
# CONFIG_PREEMPT_VOLUNTARY is not set
# CONFIG_PREEMPT is not set
# CONFIG_PREEMPT_BKL is not set
By reading the bug log, I seem to understand that this is due to stability
concerns by the Debian Kernel Team.
Do these concerns still hold, now that more than 2 years have passed?
If I read /usr/share/doc/jackd/README.Debian correctly, activating
preemption would benefit audio applications, especially:
| If you want better (or even only decent performance (fewer/no xruns, lower
| latency...), you will probably have to do a bit of work. This includes:
| 1. get recent alsa-drivers running well
| 2. set up an .asoundrc if you have a professional and
| powerful soundcard whose settings/channels/mixers you'd
| like to have finer control over.
| 3. use a 2.6 kernel with the realtime-preempt patch applied
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| 5. run in realtime mode
I would love to see Debian as ready as possible for setting up an audio
processing workstation with minimal configuration (and without recompiling
kernels or other packages).
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.22-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Reply to: