On Tue, Apr 8, 2008 at 10:36 PM, Daniel Hahler <email address hidden> wrote:
> btw: I've tried the -server images already for this very reason a few days ago: First I had to manually install l-r-m/nvidia-glx-new for it and then the
> infamous "black window" bug appeared after about 10 open windows already (while I have not seen it on -generic for a long while).
I am sorry, is this because of nvidia or is it because of the cgroup_sched?
> So, "just using the server" image does not seem to be a good solution to work around this regression, IMHO.
>
> I've tried to get the kernel teams attention for (the impact of) this issue a few days after 2.6.24 was available in Hardy and I've found out that the
> USER_SCHED setting was the reason for boinc causing my system to crawl.
> While there's a workaround for boinc now (luckily), it makes Hardy unusable for any other kind of distributed computing clients (by default) or causes
> issues like outlined above.
>
Well you can use the same workaround for all these other distributed
computing clients as well.
> Tim, I've thought you were about to enable cgroups for all kernel
> flavors, after we've talked to you on #ubuntu-kernel a few days ago?!
>
I too hope you shift to cgroup based scheduling as soon as possible.
On Tue, Apr 8, 2008 at 10:36 PM, Daniel Hahler <email address hidden> wrote: glx-new for it and then the
> btw: I've tried the -server images already for this very reason a few days ago: First I had to manually install l-r-m/nvidia-
> infamous "black window" bug appeared after about 10 open windows already (while I have not seen it on -generic for a long while).
I am sorry, is this because of nvidia or is it because of the cgroup_sched?
> So, "just using the server" image does not seem to be a good solution to work around this regression, IMHO.
>
> I've tried to get the kernel teams attention for (the impact of) this issue a few days after 2.6.24 was available in Hardy and I've found out that the
> USER_SCHED setting was the reason for boinc causing my system to crawl.
> While there's a workaround for boinc now (luckily), it makes Hardy unusable for any other kind of distributed computing clients (by default) or causes
> issues like outlined above.
>
Well you can use the same workaround for all these other distributed
computing clients as well.
> Tim, I've thought you were about to enable cgroups for all kernel
> flavors, after we've talked to you on #ubuntu-kernel a few days ago?!
>
I too hope you shift to cgroup based scheduling as soon as possible.
Thanks
Dhaval