On Saturday 17 March 2007, Mike Galbraith wrote: >Rocks and clubs at work (down boy <whack>, down i say!;). > >This is .30 with some targeted unfairness. I seem to be making progress
Try -0.31, its better yet. >toward beating it to a bloody but cooperative pulp. It might be >possible to have my cake and eat it too. Likely too ugly to live >though. > >top - 11:35:50 up 57 min, 12 users, load average: 5.20, 4.30, 2.57 > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ P COMMAND > 6599 root 26 0 174m 30m 8028 R 51 3.1 7:08.70 0 Xorg > 7991 root 29 0 18196 14m 5188 R 47 1.4 0:55.70 0 > amarok_libvisua 7995 root 37 5 3720 2444 976 R 44 0.2 > 0:27.53 1 lame 7993 root 37 5 3720 2448 976 R 40 0.2 > 0:46.60 1 lame What X driver are you using Mike? Are you on a builtin video chipset using mobo shared memory? I'm running the nvidia 9755 driver here with a jaton nvidia 6200-256 card here, and YES I KNOW that taints the kernel, but x is using on average, 1.3% of the cpu. Its sitting at a -1 nice and it continues to give usable results here in the face of a make -j8 running in another shell. With figures (over 50% cpu to X) like that, its no wonder you're squawking about it. An old phrase comes to mind "Physician, Heal thyself". Your X is broken and you are trying to blame everything but X. Fix your hardware and drivers. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Two can Live as Cheaply as One for Half as Long. -- Howard Kandel - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/