

With his patches not getting in to the 2.6, what are his plans? to get them in to 2.7? The scheduler-work has been late in the coming (when it comes to the desktop that is) in the 2.5/2.6, and I for one would like to see more and more fundamental work on this in the 2.7/2.8-series.Lovechild wrote:Okay, Nick Piggin has agreed to do a small interview since people have been asking me questions about the internals of his code.. so what do you people want to know specifically?
Well, google I guess is your friend here but basically:GoinBald wrote:What's the most powerful force in the universe?
Love!
(It's true, it drives one to surpass any limits)
(Sound's kinda like care-bear power. lol)
I'd like to know the recommended schedulers for vairous block devices
and if I may a low down on the them. You've given a overview but there's little that I've been able to find for further reading.
Where's the future heading with this...ACLs with MAC coexistance etc?
What trade-offs would be made for this...performance?
Just off the top -o- me head on a sick early morning,
j
None at all as I see it, since much of Cons work is based on making the interactivity estimator do it's job correctly - and Nick completely removed that algoritm in his scheduler... that's right we don't have the estimator at all.bssteph wrote:I'm interested if there's any chance of shoving Con's work into Nick's work and coming out with some uberscheduler.
I think I saw on LKML once (maybe from Nick himself) that the methods interfered enough so they wouldn't play nice together (both change the same thing in different ways), but maybe Con's could be tuned down a bit... ? Just wondering what the man most qualified would say.
Code: Select all
/sbin/runscript.sh: line 7: /sys/block/hda/queue/io_scheduler: No such file or directory
You need*Levi* wrote:Just booted into the new kernel, but I must've missed something cause I get this errormessage when /etc/init.d/local starts at boot:Code: Select all
/sbin/runscript.sh: line 7: /sys/block/hda/queue/io_scheduler: No such file or directory
Code: Select all
mkdir /sys
Backboost is gone so X really should be at -10 or even higher.
These comments were made upon the v12 release, but I assumed that they still held true, despite my reservations about the very idea of nicing X. So, I did try renicing X with my patched -test5 kernel but it seemed to cause poorer performance, on the basis of a casual observation involving scrolling tests and window dragging with a moderate background load.If anyone does try my patch, it is important that X is reniced to -10 or -15. Whether this will starve other things is up to debate, but it really doesn't get enough CPU if its not reniced. Email me testing experiences and CC lkml as well if you're interested in joining in.
Well, the only problem is that there's almost no traces of any 2.4-kernel left on my system. By the way, how will that resolve my choppy sound?GoinBald wrote: Oh ya Levi,
What's the issue with your sound?
A simple way that works for me but YMMV
relink your old 2.4 (scoff,scoff) kernel.
reboot into the 2.4 ker and:
follow the alsa guide for your chip then,
emerge --oneshot --nodeps alsa-driver
emerge alsa-utils
rc-update add alsasound boot
relink your love kernel and reboot into "lovin joy" again.
Well, if we assume for the moment that everything I mentioned in the previous post is irrelevant, then renicing X may not help because it could steal CPU cycles away from XMMS where it isn't merited.kerframil:
I'm using a wrapper for X renicing it to -10 and I am using test6-love1 ATM. Although the only experiences I can share is my choppy sound.
I've just disabled Mmap in XMMS and as we speak, I am recompiling the kernel without ACPI (how the heck did it get there in the first place??).kerframil wrote: Other than that, if you are using the ALSA plugin I would say do not use Mmap mode for the plugin. That usually causes all manner of problems in my experience. If that isn't the problem, then try playing with buffer sizes I suppose. And if you're using ACPI then consider trying without, that can cause odd issues with interrupt routing on some setups.
ACPI seems to be broken.