1 |
Nikos Chantziaras wrote: |
2 |
> Alan McKinnon wrote: |
3 |
>> On Saturday 27 December 2008 21:13:49 Nikos Chantziaras wrote: |
4 |
>>> I have this in my make.conf: |
5 |
>>> |
6 |
>>> PORTAGE_IONICE_COMMAND="ionice -c 3 -p \${PID}" |
7 |
>>> |
8 |
>>> Helped a bit. But still the GUI (KDE 3.5.10) gets pretty laggy. |
9 |
>>> Just a |
10 |
>>> few hours ago I updated to gcc-4.3.2-r1. Even with nice 19 and ionice |
11 |
>>> 3, lag is there. |
12 |
>>> |
13 |
>>> I hope someone finds the magic button in the kernel config to fix |
14 |
>>> that :P |
15 |
>> |
16 |
>> There isn't one - at least not one that really works. |
17 |
>> |
18 |
>> Linux mostly ignores NICE and has done so since day one. The reason |
19 |
>> according to Linux himself on some LKML post quite a while back is |
20 |
>> that Linux has a semi-decent task scheduler and nice is a 100% manual |
21 |
>> task scheduler. |
22 |
> |
23 |
> It got worse with kernel 2.6.28, btw, especially mouse cursor |
24 |
> movement. It gets stuck and skips very noticeably. Fortunately, it's |
25 |
> not a point yet where I would describe it as unusable, but if the |
26 |
> trend continues, desktop will be totally unusable by 2.6.31/32 when |
27 |
> doing something that produces load. |
28 |
> |
29 |
> |
30 |
> |
31 |
|
32 |
So it is not just me that has screwy mouse movement. I been using a old |
33 |
kernel for a while now and even thought it was just a wrong setting on |
34 |
my part. |
35 |
|
36 |
Has anyone been telling the kernel folks about this problem so they can |
37 |
fix it or roll something back? |
38 |
|
39 |
Dale |
40 |
|
41 |
:-) :-) |