yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
In r374 Franco forgot to name the script with the PowerHAL replacement and the general queue tweaks correctly. So if you reflashed your ROM or something that would explain it.

I wasn't originally going to release this, but here's a corrected r374: http://d-h.st/users/osm0sis/osmod/

It's not an osmod like before, just r374 with the hand full of small things fixed, including the corrected row value for lp_swrite. It's just a workaround for the wrong number and it doesn't contain the 950io script in any form so setting row and rebooting will give you the right number.

For those that didn't notice: lp_swrite should show up as 2. When echoing it we need to put 12 to make that happen, but since Franco hardcoded them he could just directly put 2 and it would work. That's already fixed in his git for the next build.
[Samsung Galaxy Nexus] Gafanhotz:
Damn, now I saw how lazy I'm am. I was going to ask for an flashable zip. :silly:
[Samsung Galaxy Nexus] osm0sis:
Haha I just put it in /kernel_backups/ on my sdcard and flash it with f.Ku's Backup/Restore. Simpler than recovery even. :)
[Samsung Galaxy Nexus] bigknowz:
CPU Max reverts to 1228800

Yes, flashed a new ROM yesterday. Will flash new osmod, thanks. Why was max screen off overclock stocking but not max cpu?
[Samsung Galaxy Nexus] :
Thanks again for the new Osmod. I knew somethings up with the 374 that's why I waited for yours. :D

- JFDSM™
[Samsung Galaxy Nexus] osm0sis:
I'd assume max screen off is never meant to be your max so it's only allowed to be one step down?
[Samsung Galaxy Nexus] Gafanhotz:
Yep, exactly what I did too. :)
[Samsung Galaxy Nexus] Antob125:
I used this method to get your latest mod. Was just wanting to make a request of a zip if it's possible only because it makes things easier when my ROM has an update I can flash it right there when I flash my ROM. Or else what I did today was flash original 374 then used your method again in fku to get your mod.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
You don't need to flash both. And if you want a flashable zip, just rename it to boot.img and drop it into Franco's last.
[Samsung Galaxy Nexus] Antob125:
Awesome I just did it in root explorer! Thanks so much. Never knew that's how it's done!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Charmacas:
Do anyone have a link to the mentioned thread? :)

Found my stable UV voltages btw they're running awesome. But I also want to read a bit about SR and why it is flawed. Thank you for pointing that out Osmosis!

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] ak:
http://xdaforums.com/forumdisplay.php?f=2066
[Samsung Galaxy Nexus] franciscofranco:
r375:

* Hardcode CFQ tunables, thanks usual suspects :)

* Fix the PowerHAL not being set properly on boot, my derp sorry guys

* Merge 3.0.74

* Add osmosis safety script to the .zip package

* This is probably Milestone5
[Samsung Galaxy Nexus] osm0sis:
w00t. Let me grab that real quick and check it while you're still up. :)
[Samsung Galaxy Nexus] franciscofranco:
Hit it!
[Samsung Galaxy Nexus] osm0sis:
cfq is all ****ed up. :(

Showing up as 4 / 2578 / 625 / 12582912 / 1 / 468 / 390 / 2 / 0 / 0 / 1 in f.Ku

should be entered as 4 / 80 / 330 / 12582912 / 1 / 60 / 50 / 2 / 0 / 0 / 1 but show up as 4 / 85 / 335 / 12582912 / 1 / 62 / 54 / 2 / 0 / 0 / 1

Checking your commit now..

---------- Post added at 04:23 AM ---------- Previous post was at 04:16 AM ----------

Must be something to do with those calculations you replaced with the hardcoded values since those 4 are the only ones that are messed.. :confused:
[Samsung Galaxy Nexus] franciscofranco:
Not my fault :(
[Samsung Galaxy Nexus] osm0sis:
Haha it's cool. It's just those 3 lines appear to need something else to give us the proper outcome. :)

I blame the bastards that wrote cfq in the first place for making it overly complicated in there.
[Samsung Galaxy Nexus] J-Hop2o6:
Guess we have to wait for 376 :(
[Samsung Galaxy Nexus] Charmacas:
Thank you! I've read and subscribed to the thread.

But don't understand why SR is flawed. From what I understand it works fine between 350-1350 MHz but everywhere else it doesn't. That said it would be fine for the most users.

I also read that there's a modified version of SR here on XDA which is able to handle higher and (important for me) lower MHz. So what's so flawed about SR?

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] osm0sis:
Nah, they were mistaken. Imo modded it so that it was 830 across the board for the lower limit. Scroll up and check my post in that thread; 830 isn't low enough. Pretty sure it doesn't handle higher than stock either.
[Samsung Galaxy Nexus] marcocsh:
just don't use cfq:highfive:
[Samsung Galaxy Nexus] osm0sis:
Still not fixed. :(

Franco. just drop in the fkbootscript.sh I emailed you and delete fixtunapower.sh :good:

Edit: Oh wait.. It does work because Franco just added a second call to fixtunapower.sh in init.rc instead of init.tuna.rc where the old call still is. :p Please remove that new call and use the fkbootscript.sh I sent you, Franco. It doesn't have any unnecessary "wait for android os" bull**** like the very old one you've got in there. ;)
[Samsung Galaxy Nexus] bigknowz:
PowerHAL

Is PowerHAL fixed? OK to flash r375? Haven't had a chance to flash your r374 osmod to fix the issue of max cpu above 1.2 GHz not sticking.
[Samsung Galaxy Nexus] lusca:
Hi, first of all I want to say that this is a very smooth and fast kernel, thank you for it !!

But I have some issues, if i switch to airplane mode the phone dose not react . After restart the phone starts in airplane mode, the same problem I have with the GPS and rarely with the WIFI. I must restart to enable/disable GPS,WIFI or airplane mode.

I am using PitchBlack ROM and r365, the problem persists even with 364. :(

Sorry, for my bad English and keep up the good work ! :cheers:
[Samsung Galaxy Nexus] duduzinho15:
I think is not kernel fault!
[Samsung Galaxy Nexus] akash3656:
On Rasbean and Franco 364, no such issue. And I used flight mode last night. Reflash your ROM and its gapps (if required) and don't flash Franco and try and see if flight mode works. Like the above poster, I think your ROM may be breaking flight mode.
[Samsung Galaxy Nexus] osm0sis:
Yes yes. The PowerHAL was always fine, it just wasn't getting copied in via the script (since the script wasn't getting run). Franco's got an old version of the script in there but that part works well enough.
[Samsung Galaxy Nexus] lusca:
I flashed AK kernel and I dont have any problems. So i dont think is the ROM's fault.

Any suggestions ? :confused:
[Samsung Galaxy Nexus] The Gingerbread Man:
Report it to the rom dev if you think that's the issue :thumbup:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Here's a worked-around "r375-osmod" in the same spirit as the last one. The only fixes are it has the correct bootscript (/sbin/fkbootscript.sh), removed the unnecessary extra script call from init.rc, and has a workaround for the wonky hardcoded cfq values by setting them on boot via init.tuna.rc (where Franco sets the interactive governor tunables). I had to make cfq default to do this; no big deal, just set the one you want in f.Ku/Trickster if you don't want cfq. After changing to cfq you need to reboot so the workaround can set them properly.

http://d-h.st/users/osm0sis/osmod/
[Samsung Galaxy Nexus] duduzinho15:
Cfq is better than deadline?
[Samsung Galaxy Nexus] franciscofranco:
I swear I searched my inbox and I didnt find that script. I must be blind, can you resend?

Never seen anything like that. Doesnt seem kernel related but if you like AK then stick with it.
[Samsung Galaxy Nexus] osm0sis:
They're all good. Especially since we've tuned them. See which you like best.

---------- Post added at 02:50 PM ---------- Previous post was at 02:47 PM ----------

Yup. Posted to the Group too, along with a (potential) fix for the cfq source. :)

---------- Post added at 03:02 PM ---------- Previous post was at 02:50 PM ----------

Sent! You can take that "thanks" line out of the updater-script too please. Ruins your virus gag. ;)

Should be a ui_print(""); like I originally sent. The output looks better that way.
[Samsung Galaxy Nexus] timbck2:
My phone had a weird derp when I installed 375-osmod-fix just now. I put the boot.img in kernel_backups, selected it in f.Ku, and and let it reboot. It never came back. I tried holding down the power button, holding power and V+/V- (all combinations), the only thing that worked was a battery pull. Now it's fine. Any clues?

Sent from my toro or grouper
[Samsung Galaxy Nexus] osm0sis:
Random derp. If it wouldn't come back at all I'd say bad download/flash. You could double check the md5 against what d-h has up. :good:
[Samsung Galaxy Nexus] whitedragonz83:
Happened once this weekend too. Not sure it was even an Osmod version. Like Os said, random derp most likely. I think I reflashed the kernel anyways.
[Samsung Galaxy Nexus] alfiemenace:
Hi! Can I ask a favor? I'm don't have access to a pc right now and for a couple of days, can you make a flashable zip of your r375-osmod? :) it will be much appreciated, thanks! :)

Stock ROM, custom user.
[Samsung Galaxy Nexus] osm0sis:
This. No PC required.
[Samsung Galaxy Nexus] kissme99:
Sorry for OT, but I'm curious if Google use some part of Franco's job related to the kernel? I have always wanted to know it, but I didn't know where to ask for it..
[Samsung Galaxy Nexus] The Gingerbread Man:
Iv been flashing that way as long as I can remember now, I don't even have cwm / twrp these days, all stock bar kernel
[Samsung Galaxy Nexus] thegtfusion:
Osmosis, which rom do you use?

Sent from my Nexus Prime
[Samsung Galaxy Nexus] lippol94:
If he doesn't mind.. I can answer for him :)

He usually runs a 100% stock ROM. Directly from google ;)

That's what it makes his statements pretty much reliable. His doesn't mess up with crappy feature-pumped roms :angel:

And I can totaly share his point of view. On my side, I'm running latest Minco V7 which is not actually stock, but it's really close! Best decision of my life with this phone!
[Samsung Galaxy Nexus] thegtfusion:
Where is minco v7? The thead says still v6??

Sent from my Nexus Prime
[Samsung Galaxy Nexus] lippol94:
They changed home :)

You can find it on their own new place: minco.mobi

http://forum.minco.mobi/viewtopic.php?f=12&t=6
[Samsung Galaxy Nexus] thegtfusion:
Does it have the gcc 4.7 + bionic/krait optimazations?

Sorry for ot

Sent from my Nexus Prime
[Samsung Galaxy Nexus] bigknowz:
CPU Max fixed

Thanks franco, osm0sis - 375 working well. Overclock is sticking again.
[Samsung Galaxy Nexus] kashifsiddique:
hello guys,noobie question, just want to ask, whats the purpose of boot375.img and other .img's in the link, and how to use it?
[Samsung Galaxy Nexus] Milleniumlance:
the img files are for use with the franco updater app, you can flash the new kernel straight from the app using the img file
[Samsung Galaxy Nexus] rene_r:
Edited...
[Samsung Galaxy Nexus] Milleniumlance:
under kernel backup and restore, download into the folder 0/kernel _backups
[Samsung Galaxy Nexus] rene_r:
Thx I must have been blind;)
[Samsung Galaxy Nexus] franciscofranco:
Ok me and osm0sis tackled down what was left to do for Milestone so heres r376, should be the last before the labeled stable release:

r376:

* Minor fixes and final bits preparing for Milestone

* Update BFQ to v6
[Samsung Galaxy Nexus] Khrushy:
Boom. New bfq to play with ^^

Great stuff Franco.
[Samsung Galaxy Nexus] osm0sis:
Oh snap. This **** is delicious.
[Samsung Galaxy Nexus] Degrated Shadow:
is there really any way to fix real racing 3 for this kernel??? i really really enjoy the game as much as i love franco's kernel...but really the gaming thing isnt neatly going with this kernel.. any possible solution? and franco thanks for these update and fast kernel.. its just this one issue that makes me change kernels specifically for gaming purposes and then make me flash back to yours for fluid ui
[Samsung Galaxy Nexus] Khrushy:
Can someone confirm something for me quickly?

Change your io scheduler, and change one of the tuneable values then Reboot.

For me, the scheduler change is sticking after reboot, but tuneables aren't.

Can anyone else confirm this behavior?

Cheers.
[Samsung Galaxy Nexus] galakanokis:
It says in Françoisw app that tune ables for schedulers are reset on boot. I think the only way to change them on boot is through a script.

Haven't run Franco in awhile, this is nice. Feels good to be back.

G man
[Samsung Galaxy Nexus] Khrushy:
Of course - I've been setting my tuneables with a script for so long I forgot that entirely. **** me I'm a dumb bastard sometimes.

Cheers.
[Samsung Galaxy Nexus] galakanokis:
No worries man, we all brain fart every now and then.

G man
[Samsung Galaxy Nexus] JBNex:
BFQ rocks on latest kernel! Keep it up! :D
[Samsung Galaxy Nexus] whitedragonz83:
Wtf. Just a few short tests I try upon reboots and BFQ is killing it.
[Samsung Galaxy Nexus] duduzinho15:
Now this thread is come back to be like old times! :)

I got reboot with bfq on 376 :(
[Samsung Galaxy Nexus] whitedragonz83:
Franco. Did you update BFQ because of a Google fairy dropping a hint that Key Lime Pie would use that as default?

:)

#rumor
[Samsung Galaxy Nexus] Khrushy:
For those giving bfq a go - try setting back_seek_penalty =1 (default = 2) and slice_idle = 0 (default = 7). The rest of the defaults are pretty good it seems.
[Samsung Galaxy Nexus] ppsx:
Got many reboots on bfq@376...

pps@sgn
[Samsung Galaxy Nexus] bigknowz:
Deadline test

osm0sis, new deadline values seem laggy. When doing a few different things, background turns black before wallpaper and icons redrawn. Moved back to cfq and phone seems better. If anything changes with cfq, I'll comment again.
[Samsung Galaxy Nexus] sym_m:
r376 run smooth no lag very smoooth i like this kernal.,, Q: CFq or bfq what the better
[Samsung Galaxy Nexus] The Gingerbread Man:
Use cfq / row for now for a smooth experience. Deadline values are being worked on and how ever they end up I promice it will be fast ;)
[Samsung Galaxy Nexus] Khrushy:
CFQ we've thoroughly tuned up, and is very good.

BFQ is essentially a more advanced version of CFQ, but we have haven't optimised the tunables for it. I made a couple of basic suggestions for BFQ a few posts up, but essentially that seems to just bring it close to the fully tuned up cfq. Also, this is the first version of franco with BFQv6 in it, so there may be some hiccups we haven't encountered yet.

As always though, test both and see which you like, but there shouldn't be too much difference between them I don't think.
[Samsung Galaxy Nexus] logi43:
I'm using R376 with BFQ and the performance is very good, fast and fluid, the configurations are included in this kernel osmosis?

Edit : I just had my first reboot back to CFQ
[Samsung Galaxy Nexus] Khrushy:
The kernel currently includes the tuned values for RoW and CFQ. Deadline is currently being worked on and should be finalised by next release.

BFQ has just been updated to BFQv6 by Franco, but the tuneables are just the Google defaults for bfq and nothing has been done on improving them.
[Samsung Galaxy Nexus] Angelakaro:
Not bad, but i had a freeze while listening to music and surfing the web, my phone vibrated and rebooted (with google logo)

Now i'm using stock values and i'm just doing the same things as before without any issues,maybe was just a random issue, not complaining about these values. Other people is having trouble even with stock values. No last kmsg was generated

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] bombadier:
Just had a reboot using BFQ,I downloaded default manager lite from the play store went to open in and reboot, after the reboot TCP Congestion Avoidance was reset to cubic(been using westwood for a long time) will change to CFQ and see if that is more stable/better
[Samsung Galaxy Nexus] The Gingerbread Man:
All these people with reboots with BFQ, can you upload here Proc/last kmsg please. Need more info to see what's wrong. Thank you
[Samsung Galaxy Nexus] Khrushy:
I had one earlier in the day. Kmsg attached. I didn't see anything interesting in it.

It hasn't happened a second time, so I wasn't going to make a deal of it, but if others are getting it too then hey, here goes.

http://db.tt/L6xbp00c
[Samsung Galaxy Nexus] The Gingerbread Man:
So far I can see this;

[ 815.798675] Kernel panic - not syncing: Fatal exception

[ 815.798828] CPU1: stopping

[ 815.798919] Backtrace:

[ 815.799102] [<c0062f70>] (dump_backtrace+0x0/0x12c) from [<c0627084>] (dump_stack+0x18/0x1c)

[ 815.799285] r6:c0055fe4 r5:c598a000 r4:c086bd28 r3:00000000

[ 815.799682] [<c062706c>] (dump_stack+0x0/0x1c) from [<c00589a8>] (do_IPI+0x1e0/0x218)

[ 815.799865] [<c00587c8>] (do_IPI+0x0/0x218) from [<c005e7a8>] (__irq_usr+0x48/0xe0)

[ 815.800018] Exception stack(0xc598bfb0 to 0xc598bff8)

[ 815.800109] bfa0: 411cdb20 00000517 51700005 00000001

[ 815.800262] bfc0: 51700005 00000000 2a5489c0 5cd47e94 000000d4 5cd47e88 00000000 5d1b1c7c

[ 815.800445] bfe0: 00000001 5d1b1c00 40856a01 40857d48 280e0030 ffffffff

[ 815.800537] Rebooting in 5 seconds..

[ 819.912750] Restarting Linux version 3.0.74-franco.Kernel-nightly (francisco@francisco) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #376 SMP PREEMPT Mon Apr 22 22:09:09 PDT 2013

[ 819.912750]

No errors detected

Boot info:

Last reset was warm software reset (PRM_RSTST=0x2)

I'll see what else is in there, look for the cause if I can
[Samsung Galaxy Nexus] osm0sis:
Scroll down to the bottom. There is some obvious **** going down. Good log bro! Hopefully Franco can figure something out. :)

Edit: This seems like the first sign of something going wrong:

[ 815.661376] Unable to handle kernel NULL pointer dereference at virtual address 00000038
[Samsung Galaxy Nexus] bombadier:
http://goo.gl/9wNI7 hope this is of use,had to reboot my phone again as it seems to of had a meltdown,I changed to CFQ and was trying to get the log when phone became unresponsive and I had to reboot,the log may not be of use for debugging the original reboot,

Thanks in advance
[Samsung Galaxy Nexus] Gafanhotz:
I couldn't attach logs yet (deactivated all of them a long time ago) but as soon as I get a reboot I'll attach. But it's obviously an NPE as I could see on the others log.
[Samsung Galaxy Nexus] sconrad308:
Last night I updated to r375 and this morning at 4 something my phone was charging and wasn't using anything, in fact I was sleeping. Anyway when I got up my phone wouldn't reboot. Could it have been r-375? I'm worried about re doing the kernel until the stable release. Can someone please give me some advice.

Thanks.
[Samsung Galaxy Nexus] osm0sis:
Just got this via PM from a new user:

Flash stock kernel with fastboot. If that doesn't fix it then it can't be franco.Kernel's fault.

Edit: Wait.. ejatd, did you perhaps try to flash r376 on <JB4.2.2 and then PM me about it when it's in the written into the topic and OP? :p

Edit 2: Nope he says 4.2.2. Weird.
[Samsung Galaxy Nexus] Angelakaro:
R376,stock deodexed 4.2.2..Another freeze with bfq (stock values) here's /proc/last_kmsg: http://db.tt/k8ypiElo

(Actually it was generated also when i had the first freeze, but i thought it was an older one)

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
If BFQ gives freezes and what not then just dont use it. Old deadline and row just works fine.
[Samsung Galaxy Nexus] rossrogers:
Does CFQ vs ROW have any noticeable difference on CPU load.

Both seem super smooth and fast, I get a little slow down still when Google Play updates stuff using ROW, but not a big deal, no freezes.

Just curious if there is a way to know which would be more "battery friendly" or point me in a direction of how to assess this for myself. Would the CPU monitor stuff Franco built into the app suffice?

Thanks.
[Samsung Galaxy Nexus] Angelakaro:
Of course, but bfq v6 seems so good..it gives good overall smoothness and responsiveness. What a pity

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Please check Khrushy's last_kmsg on the last page. It's got a full backtrace and everything so you might be able to figure out why BFQv6 is causing NPE and reboots.
[Samsung Galaxy Nexus] sishgupta:
This thread is for discussion of Franco's Kernel not rogue partial wakelocks.

If you are having trouble with wakelocks you should take it to another thread.
[Samsung Galaxy Nexus] PapaWangsta:
Hey guys, need your opinion!

I have "franco kernel updater" and "setCPU", would it be conflicts of each other? Should I uninstall "setCPU"?
[Samsung Galaxy Nexus] Elganja:
no random reboots here either
[Samsung Galaxy Nexus] Jrbourque:
None here
[Samsung Galaxy Nexus] jhericurls:
I was interested in finding out what this fuss about Wheatley was, so I installed the GLaDOS kernel.

In terms of overall battery efficiency your #13.1 is still better, maybe it's the UV. But I was getting slightly better screen and standby time with #13.1.

Ran the GLaDOS kernel for 2 days and not had stability problems.
[Samsung Galaxy Nexus] franciscofranco:
That's not going to happen. I made my tests, sent them to few testers and the results were not that good, so after deep thought I just removed it.

I'm sorry as its something I can't reproduce I can't fix/advise.

They won't conflict, but you don't need both.

Yes, those were my conclusions as well, with all due respect to Ezekeels work.
[Samsung Galaxy Nexus] ro_explorer:
He he .. and I have real numbers to support that (look at the mp3 play tests) :)
[Samsung Galaxy Nexus] franciscofranco:
Good numbers, thanks for taking the time.
[Samsung Galaxy Nexus] taney:
Hi! I'm trying to figure out if my issue is kernel, hardware, or ROM related. Basically, my battery drain is fine but when it reaches about 30%, the phone completely dies and I'd have to charge it. When I get enough charge to boot, the battery reads 0%.

I'm running CM9 Kang (codeworkx 012212+cmparts) and Franco.kernel 13.1.

Anyone else have this issue?
[Samsung Galaxy Nexus] Fabipro:
Bought your app, very nice. Hope to see your "big" update soon :)

Now I'm on stock settings on 13.1. Will test it tomorrow .. we will see .. thanks!

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] Vangelis13:
Calibrate the battery? I haven't seen that issue in any of the kernel threads..
[Samsung Galaxy Nexus] sluflyer06:
Already been debunked that the whole calibration thing is anything but. The stats file does not have anything to do with the way the phone reads the discharge, its pretty much just a file with the information that you see in Settings>Battery and by default (even stock) is reset anytime the phone is unplugged is and 'mostly' charged.
[Samsung Galaxy Nexus] Nebucatnetzer:
And before anyone is asking. Here's the link to this information.

https://plus.google.com/u/0/105051985738280261832/posts/FV3LVtdVxPT

In case you don't know here. She's a "real" android dev and working for Google.
[Samsung Galaxy Nexus] franciscofranco:
Thank you for the link.

Ok #14 is ready. Preparations for upload initiated.
[Samsung Galaxy Nexus] MarcLandis:
Go Go Go :)

Marc
[Samsung Galaxy Nexus] franciscofranco:
Ok #14 is out :)
[Samsung Galaxy Nexus] Felixpau86:
Feels smoother. Thanks
[Samsung Galaxy Nexus] meilstone:
dunno why, but pferformance governor was setted default even though u recommend conservative
[Samsung Galaxy Nexus] Felixpau86:
Confirmed its using performance on mine too and by the looks of cpuspy its going full tilt at 1200 or its deep sleeping.
[Samsung Galaxy Nexus] loudaccord:
I think everyone is DLing at the same time :)
[Samsung Galaxy Nexus] The Gingerbread Man:
Pull battery and reboot. Check which android version you are flashing to, all the recent kernels are for 4.2.2. Did your phone just run out of battery? Charge it maybe. Milestone is close now

Thats because ROW will favour Read Over Write (row) so I guess that can't be helped. CFQ is overall smoother I beleive

Wait till what ever the new deadline tunables are released. We have some very good data ;)