UDS Developments

[Kaj Ailomaa]

On 05/09/2012 05:50 PM, Len Ovens wrote:
>
> On Wed, May 9, 2012 1:39 am, Ralf Mardorf wrote:
>> On Tue, 2012-05-08 at 22:02 +0200, Kaj Ailomaa wrote:
>>
>>> # CONFIG_NO_HZ is not set
>>
>> I and many others used NO_HZ yes for a long time without any issues. For
>> testing purpose I switched to not set too.
>
> There are still some tweaks we need to look at. I noticed that one as
> well. We tend to be blind to some things. This one affects midi more than
> audio as I understand... probably why we missed it.
>
>> Don't forget to enable hrtimer/hpet modules and not to set all kinds of
>> trace/debug options.
>>
>> Default CPU frequency scaling should be performance, but ondemand should
>> be possible to.
>
> Yup.
>
>> If "threadirqs" wouldn't be compiled as a string to the kernel, it would
>> be possible to boot without threadirqs. Dunno, but this might be an
>> advantage for a recovery boot or if performance of the GUI sometimes is
>> more important than threading for audio work. This might enable t simply
>> use different boot options instead of using different kernels.
>
> As we are also a graphics distro (or trying to be) it may be worth while
> configuring grub to have three options per kernel. Graphics, Audio and
> Recovery. Our main idea with making threadirqs a boot option was that it
> would be easier to auto build because it is then the same as the normal
> ubuntu kernel (no patches required) just a different config. But, you have
> pointed out another reason.
>
> Len
>

I've also recenlty discovered that "threadirqs" and the rtirq script are 
actually making one of my machines misbehave, something that I've never 
heard of before, so it might be a good idea to think about having that 
as a tweakable option between boots, since it might be causing problems 
for some machines, that normally don't need it enabled.