If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

in block/blk-softirq.c
This code is for HyperThreading CPUs only and may fail on dual (or more) core CPUs. Also I couldn't test it yet as the netbook is slow and I have to do a lot more before I'm able to reboot.

Originally Posted by kernelOfTruth

I DO care about tickless :P

best compromise about interactivity, smoothness and energy savings

otherwise I could also use the rt-kernel

or aren't there that much energy savings with tickless enabled ?

Here I copy a whole things from the prev thread.

This is RIFS-V3-Test(Actually is V5) based on RIFS-V2
It solved the interactivity problem RIFS-ES has.

smecenter has a point - overall RIFS-ES is a very smooth and great scheduler

to make it the best it is paramount that the max latencies also get smaller

I'm currently still using it with 3.4.2 and it's working great but from time to time there are small noticable lags during heavy i/o (the same with BFS & CFS)

it's not RIFS-ES/the cpu scheduler's fault if the i/o or VFS subsystem, device-mapper, etc. etc. screw up and lead to delays but it would at least be nice if the cpu scheduler could manage to keep latencies to a minimum on its own

smecenter has a point - overall RIFS-ES is a very smooth and great scheduler

to make it the best it is paramount that the max latencies also get smaller

I'm currently still using it with 3.4.2 and it's working great but from time to time there are small noticable lags during heavy i/o (the same with BFS & CFS)

it's not RIFS-ES/the cpu scheduler's fault if the i/o or VFS subsystem, device-mapper, etc. etc. screw up and lead to delays but it would at least be nice if the cpu scheduler could manage to keep latencies to a minimum on its own

any ideas on how to improve it more ?

otherwise it's awesome

thanks !

Heavy IO task always sleep with TASK_UNINTERRUPTIBLE. We can adjust the scheduler by this clue.
But still RIFS-v2 performs the best on your machine, isn't?
You may also see DMS SCHEDULER on the download page.

Heavy IO task always sleep with TASK_UNINTERRUPTIBLE. We can adjust the scheduler by this clue.
But still RIFS-v2 performs the best on your machine, isn't?
You may also see DMS SCHEDULER on the download page.

ok, I see

making it TASK_UNINTERRUPTIBLE would probably solve the issue with input lag during heavy i/o - especially under the amd64 architecture (intel only ?) - once and for all

provided of course that all the i/o (especially writing) is marked TASK_UNINTERRUPTIBLE

yeah, it's the best scheduler so far

what does that DMS Scheduler exactly change ? from what I read it prioritizes user input somehow and is swap aware ? is that correct ?