yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Kurre:
One could add some if [ -e /sys/.../file ] checks to prevent these errors..but anyway, if those errors doesn't bug you then checking for those files isn't needed :)

I'm personally building my own "tweaks" script with some checks/fallbacks and other things to control it easily (via tasker/command center/terminal) at reboots. I hope that I can come up with some nice system where I can easily choose if want to keep an active scheduler at reboot or fallback to the preset one. Most likely this is quite useless work, but anyway it's fun to do and learn at the same time :p
[Samsung Galaxy Nexus] pkgnex:
I've found that re-enabling front merges seems to be an improvement, as is raising fifo_batch to a low number (between 1 and 4 seems to feel good) . Much higher on the fifo_batch introduces some lag when multitasking.
[Samsung Galaxy Nexus] osm0sis:
Agreed. We originally had fifo_batch at 1 (before messing with the general queue options), but now I'm liking it at either 2 or 4.
[Samsung Galaxy Nexus] pkgnex:
Same here. Running 4 at the moment, may like 2 a little better. I want to run at least a half day each way before I form a solid opinion, though.
[Samsung Galaxy Nexus] bigknowz:
Adjustments

Are the new settings specific to cfq or for deadline and row as well?
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

This thread is becoming so boring :P just joking,i don't understand anything of what you're talking about lol ,keep up with the good work ;)

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] Sik-1:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Half of the time I don't understand wat doctors and scientists are talking about lmfao but they sure know their sh*t :thumbup::p:D
[Samsung Galaxy Nexus] pkgnex:
The fifo_batch and front_merges discussion is for deadline.
[Samsung Galaxy Nexus] grognaz:
hi, i have a little problem with your kernel franco.

when i install your kernel the write speed is reduced dramaticly to about 1mb/s. to test this i flashed to komplete stock and also tried an other kernel from the clean install and so far the slowdown happens when i install your kernel r366.

i really loved the stability and performance of the kernel but this makes it unusable for me. so i hope you can look into this problem and fix it.

i attached to pictures of a speed test (before and after installation of the kernel) so you can see the difference.
[Samsung Galaxy Nexus] bigknowz:
New Settings

These new settings correct?

# general queue tweaks

echo 0 > /sys/block/mmcblk0/queue/nomerges;

# deadline tweaks

echo 1 > /sys/block/mmcblk0/queue/iosched/front_merges;

echo 2 > /sys/block/mmcblk0/queue/iosched/fifo_batch;
[Samsung Galaxy Nexus] Fenvarien:
AW: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Regarding fifo_batch I tested 6 and 4 today (with front_merges 1), 4 worked great while 6 introduced some lag. No freezes happened even with heavy playstore updates :good:
[Samsung Galaxy Nexus] osm0sis:
Nice! Please let us know about 2 vs. 4 as well. :)
[Samsung Galaxy Nexus] Raijin:
The link of settings in malaroth signature is always the same? https://www.dropbox.com/s/h2sytxb65ym93ew/950iosettings

I ask this to make a bookmark to check if there's updates everyday.
[Samsung Galaxy Nexus] Zadeis:
OK I'm just coming back to this now but just wanted to contribute with rq affinity being 2 and iostats and nomerges being 0.

Testing out deadline again with malroths current values but having set front_merges to 1 and testing out the fifo batch settings at either 2 or 4.

Over all I think 4 was a bit better. I typed out a text message while it was both downloading and installing the app. Still had hiccups but for the most part seemed OK.

Something to be aware I noticed the download takes much longer with those deadline settings. just to see I uninstalled office suite (the app I uninstall and re install to test things) and then reinstalled it to notice the download was slower but with row it downloads plenty quickly.

Just something I observed and if this was said already I apologize as I have been busy with stuff before spring break.
[Samsung Galaxy Nexus] osm0sis:
File URL will change but you should always be able to grab it from my public files; here's the latest (14-Mar-2013):

http://d-h.st/users/osm0sis ;)
[Samsung Galaxy Nexus] Edward Stanbury:
thanks bro, love having the most up to date settings :P
[Samsung Galaxy Nexus] pkgnex:
I think I prefer 2 over 4, but the difference - if any - is minor. 2 just feels a little faster to me than 4 does when I've got several things open, at least in terms of the responsiveness of the app I'm actively using.
[Samsung Galaxy Nexus] osm0sis:
Yup I felt the same way about back_seek_max and slice/group idle. Couldn't really tell any difference so in the 13-Mar-2013 file above I just went with what theoretically made the most sense: slice_idle 0, group_idle 7, and back_seek_max at something huge, but trying it at something even based on your testing, so instead of the 2TB - 1KB absolute max, it's 2TB - 2KB. Also went with nr_requests 512 based on your and Zadeis' testing.

Still totally open for testing and opinions on the different possibilities of back_seek_max and slice/group idle though, or anything really. These are just what I'm trying for now.
[Samsung Galaxy Nexus] mixtapes08:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Sorry for the noob questions but i been busy this past few weeks and i dont know what general queue tweaks are for..?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Search the thread for posts by me with the words "light reading" ;)

If I had to sum them up I'd basically say they just make schedulers behave better for flash memory since the schedulers were designed for rotational disks. Platters would suffer slowdowns from seeking back too far from where the head is currently, etc. so the queue/schedulers try to compensate for that, but flash of course doesn't have a head at all, and is much, much faster, so shouldn't be constrained by things like that.
[Samsung Galaxy Nexus] Sik-1:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

If the schedulers are designed for rotational discs wouldn't noop be idle????
[Samsung Galaxy Nexus] reysonance:
Isn't noop primarily designed for non-rotational media from the get-go? Ramdisk etc

Different schedulers for different purpose, no?
[Samsung Galaxy Nexus] osm0sis:
Yup that's right I think. I was just speaking generally, the queue settings aren't optimized for flash media and cfq isn't built for it either but can perform quite well with some tweaks.
[Samsung Galaxy Nexus] taz1458:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

There a reason why under jbsourcery 5.1, it will connect to Wi-Fi, but won't process anything? It will connect but the data won't transmit. had Irvine cfq and interactive those are the only changes I made.
[Samsung Galaxy Nexus] Sik-1:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Yes it does perform quite well with the tunables, feels like the donut days on the g1 again lol
[Samsung Galaxy Nexus] marcusva79:
Like Franco's kernel but phone lagged like crazy after r366 what are some great tweaks
[Samsung Galaxy Nexus] osm0sis:
Read.
[Samsung Galaxy Nexus] LibertyMonger:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I have Xylon on my nexus s and galaxy nexus and it seems to run better on my nexus s. So it doesn't shock me
[Samsung Galaxy Nexus] Ruggerxpunk:
My buddy has an S III and uses ktoonz kernel. That dev posts governor settings for awesome battery/performance. Does anyone have a detailed list of governor settings for this kernel that works good?

I did see the link in osm0sis signature for his settings, but I was wondering if anyone had alternatives.
[Samsung Galaxy Nexus] Fenvarien:
+1

After testing fifo_batch 2 vs. 4 I finally settled with 2. It feels just a little bit snappier in demanding multitasking situations.
[Samsung Galaxy Nexus] pkgnex:
With merges turned back on, I've gone back through the cfq tunables still under debate. Now I see no difference with the idle parameter settings (if there ever was one... but I think 0 for both was best when merges were off). I'm on board with slice_idle = 0 and group_idle = 7. Testing back_seek_max at your 2Tb - 2kb, full memory and half memory for my device (32Gb and 16Gb respectively), the i/o benchmarks in antutu are still best with the half memory value (16777216). Difference is about 7% when averaging 6 runs vs either full memory value or 2Tb, and full mem and 2 Tb are within 1%.

I think we nailed deadline with fifo_batch = 2 and front_merges = 1 with nomerges set to 0, and RoW is still performing awesomely.

Any plans for BFQ? Any "light reading" links you can share?
[Samsung Galaxy Nexus] whitedragonz83:
I liked the recent Deadline changes too, but still am preferring ROW at the moment. Feels great.
[Samsung Galaxy Nexus] osm0sis:
Hmm I saw absolutely no difference in the results from AndroBench, just the usual variability with full memory for my device (16777216), half that (8388608) or the 2TB - 2KB near-max (2147483646). I thought the near-max feels better than the absolute max, and 16GB (my full) felt better than 8GB (my half), but again, found the near-max, the flat ~1TB (1000000000), and 16GB indistinguishable. Anyone else with a 32 or 16GB GN in here who can try those 3-4 values for us?

As for bfq it's already faster than I remember thanks to the queue tweaks, but it's based on cfq so you could make the same tweaks to it roughly as a starting point. I did this the other day out of curiosity and found it pretty favorable. Haven't got any extra reading for it yet though. ;)
[Samsung Galaxy Nexus] pkgnex:
Actually, in addition to the queue tweaks, BFQ & CFQ share some scheduler parameters as well. Running the io benchmarks with the carryover cfq tunables applied to bfq (for the shared parameters) results in at least a 25% improvement vs the kernel default bfq values, which is an outstanding start for bfq, and cuts the parameters left to "tune" in about half. BFQ is already benchmarking in the vicinity of cfq and deadline now, where it had always previously lagged well behind all the other schedulers.
[Samsung Galaxy Nexus] Fenvarien:
AW: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Regarding BFQ: In February 2013 bfq v6 was released, which incorporates many changes, improvements and bugfixes in comparison to v5, which is currently implemented in f.K.

http://algo.ing.unimo.it/people/paolo/disk_sched/patches/3.5.0-v6/README.BFQ
[Samsung Galaxy Nexus] pkgnex:
Yeah, I saw that too when I was looking into bfq today.

Os, what do you think the odds are of getting Franco to commit bfq v6 to the next nightly?
[Samsung Galaxy Nexus] osm0sis:
Really? I didn't realize f.K was even all the way up to v5. :eek:

Great link. Has some flash-related tunable tweaks written right into it. :)

Franco's been pretty crazy busy with work so I don't know what's up for the next nightly or when it will be but I'm sure a new revision like that will make it in eventually.

Edit: Can you guys also all try 350/3500/6/0/2 vs. 350/3500/4/1/2 for deadline with the general queue tweaks in the latest 950iosettings? Or if you want to get in depth, we need more opinions/testing on writes_starved 6 vs. 4, and front_merges 1 vs. 0. fifo_batch 2 definitely seems like the winner. :good:
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Noop is designed with one thing in mind. There is only one function and that is nomerges. You cannot alter or change it. That is it's sole function and was designed that way. "Ideal" is subjective, nobody uses their phone the same way as everyone else.

On another note raikon bookmark osm0sis' site he posted. I just ended a 2 year toxic relationship and am finding it hard to focus on schedulers and updating my files and stuff. Still tweaking a lil but not as intensive. Osm0sis gingerbread man and shreddintyres are still the ones to go to if Franco or I don't respond
[Samsung Galaxy Nexus] dracon6ai:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Om and Mal worked up some nice scripts to make r366 usable, if your like me though and don't like messing with kernels (few speed bumps and that's all) then I'll stay away from r366 for now. It's still a beautiful kernel but the write speed issues make is not as desirable as other kernels that don't suffer from it. As I said before though, Os and Mal got scripts that bring r366 back to life. I'm personally just waiting till r367 to see if Franco fixes it.

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Somehow I ****ed up my fku app. It froze while in the app, had to battery pull and when my phone booted up data of apps was gone.. The f.Ku app was gone. I just restored some data, but f.Ku I can't install from play store, it gives error 24. Other apps install well. I think there are some leftover binaries from the app somewhere. How can I remove that, clean things up? Pretty ****ty without the app.

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] reysonance:
Try manually removing apps from /data/app/, worth a try.

---------- Post added at 04:20 PM ---------- Previous post was at 03:51 PM ----------

I'm trying out the deadline tweaks, and after a dozen benchmark runs (with A1 and AndroBench), I'm impressed.

4/1/2 has an average write speed of around 12,29 MB/s, while with 6/0/2 it's 15,90 MB/s, with the highest write speed clocking in at 17,7 MB/s.

I'm on 3G right now so I can't see how it fares against large downloads from the Play Store though.
[Samsung Galaxy Nexus] Kurre:
sounds like data corruption..fsync off before freeze?

And as said, manually clearing from /data should do the trick :)

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I had fsync on, that's the strange thing. Also there's no sign of f.Ku in data/app, all ready tried that. The free app is installing well.

Verstuurd van mijn Nexus 7 met Tapatalk
[Samsung Galaxy Nexus] testamentg:
I encountered the same trouble. Cant reinstall 1 app while others can be installed properly. This is not a kernel issue, for sure, since I had this on AK.
[Samsung Galaxy Nexus] Fenvarien:
AW: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

4/1/2 performs much better for me than 6/0/2 when Playstore updates come into play. To avoid the risk of freezes I'd definitely keep 4/1/2. As always it's a tradeoff between performance and compatibility...
[Samsung Galaxy Nexus] JBNex:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

How do you set an i/o scheduler (not its settings) on boot? Or does it persist through a reboot? For some reason the init.d. Script isn't applying the settings.
[Samsung Galaxy Nexus] reysonance:
/sys/block/mmcblk0/queue/scheduler

Echo your desired scheduler there, e.g. 'echo "deadline" > /sys/block/mmcblk0/queue/scheduler'
[Samsung Galaxy Nexus] Khrushy:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4r300 -&gt; 4.1

The io script in malaroth / os' settings script doesn't set the scheduler. To set the scheduler, go into f.Ku under "custom kernel settings". Yes it persists through reboots provided nothing else overwrites it.

As an aside, I'm currently using noop, and finding it surprisingly excellent. It's a toss up between that or cfq for me.
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Yes... you have to set the scheduler in whatever app you're using (f.Ku) as "deadline, row etc" then on reboot the script sets the values for whichever scheduler you've chosen.

---------- Post added at 07:07 AM ---------- Previous post was at 07:04 AM ----------

Rey go back and enable nomerges, run 351/3000/6/0/0 and I'm gonna link a script for you in pm on vm settings, they aren't public consumption yet sorry guys I'm the only one using them. Tell me what your results come to. That's the best setting for my Gnex even though others are getting different

---------- Post added at 07:07 AM ---------- Previous post was at 07:07 AM ----------

Rey go back and enable nomerges, run 351/3000/6/0/0 and I'm gonna link a script for you in pm on vm settings, they aren't public consumption yet sorry guys I'm the only one using them. Tell me what your results come to. That's the best setting for my Gnex even though others are getting different
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Did you fixed it? I'm to lazy to wipe anything else than my butt .

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] Kurre:
check also /data/data for a com.franco.kernel folder and delete it if found. Dunno where else leftovers would be :confused:

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] pkgnex:
I think with nomerges enabled (set to 1) 6/0/0/ was the best.

However, with nomerges disabled (set to 0), I like 4/1/2 much better. This one is my choice (with 6/1/2 being pretty much indistinguishable), as having nomerges disabled is working much better for me with ALL the schedulers.
[Samsung Galaxy Nexus] reysonance:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

@malaroth with the VM tweaks, 6/0/0 performs pretty well with higher write speed, although oddly enough, on benchmarks, the read speed fluctuates and drop from time to time, which seems only happen with 6/0/0 + your VM tweaks, I can't reproduce the drops with any other combination. It also doesn't stutter as much compared to the stock setting when apps are being written to /data.

And like pkgnex, no_merges disabled and 4/1/2 takes the cake for me, stutters significantly decreases, it's there, but barely noticeable. Although I must note that both combination still stutters quite heavily when CyanDelta is merging .zip, or when TB is doing it's scheduled backup, which doesn't happen (this severely, at least) on stock kernel.
[Samsung Galaxy Nexus] vlc_marcos:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Does anyone has the problem of a big draining of the battery, in what I the battery status shows that it was charging without been connected and the screen turns on without any reason?
[Samsung Galaxy Nexus] reysonance:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Most likely a hardware problem, it's pretty common, the screen turning on also caused by it.

Try cleaning your USB port, with rubbing alcohol or some sort. And on CM (or AOKP?) there's an option to disable the screen wake when an AC adapter is detected, that should fix your screen wake problem.
[Samsung Galaxy Nexus] CADude:
Hmmm, longest time I've seen this thread without a kernel update.
[Samsung Galaxy Nexus] peikojose:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Sad but true
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

That's OK... this is about finding the sweet spot for everyone. Not everyone has to run the same values though. Whatever works best on your device
[Samsung Galaxy Nexus] Langduscher:
What major improvements could possibly be made to this kernel? It already is damn good & stable.

Besides if you want frequent changes and improvements, join all the tuning that is going on :good: you can either wait for Francisco or implement/ help improve the tunables (basically comes down to the same thing as a "new" kernel release).
[Samsung Galaxy Nexus] osm0sis:
And just to make it more tricky, we also need the sweet spot for all the schedulers. :p

We can't rightly cripple cfq and bfq to make deadline better; so I think nomerges will have to stay at 0 and we'll need to figure out what we can do with deadline from there. Everyone's Play Store issues exploding with r366 (when Franco implementing the nomerges tweaks) seems like pretty good evidence for that as well.

The other component for why deadline isn't as good as we remember with nomerges disabled definitely has to be the vm tunables. vfs cache pressure used to be 300 but franco reverted to the stock 1. It would probably do us well to revert to an earlier build, dump the vm tunable values and see which ones we would like to bring forward.

I definitely agree with your sentiment. :)

There are a few things we could fix up though, foremost being said tunables. ;)

I'd also like a screen off min freq, and the -discard option added to the mounts so that the people with the newer GNs and the EMMC chip bug are better covered.
[Samsung Galaxy Nexus] Khrushy:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

On that note, what VM values are you running ATM? Defaults from 366 or something else?

I set different VM values and found it to make a massive difference when combined with row/cfq/noop. Deadline seems to be the redheaded stepchild of the family which needs completely different settings, and I don't have the time to fool with it ATM.
[Samsung Galaxy Nexus] peikojose:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Antutu doesn't run when I flash Franco kernel (it gets stuck at sd card tests) with the last nightly of CM10.1
[Samsung Galaxy Nexus] J-Hop2o6:
Turn off "Check Network Time" before the test. I dunno why it does that, or what it really is.

---------- Post added at 11:27 AM ---------- Previous post was at 11:24 AM ----------

@ Osmosis

I DL'd your iosettings (mar 14), and I did the correct stuff (init.d folder, rwxr-xr-x), but the values aren't sticking (checked via franco app). How SHOULD it look like inside the file? I want to use the CFQ tweaks and the general tweaks. And if its possible, have it set the rest of the IO tweaks also. I had the tweaks stick before. I don't know why its not sticking this time.
[Samsung Galaxy Nexus] peikojose:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

It worked... Antutu ran..

But I am getting really bad SD read numbers... Under 2mb/s
[Samsung Galaxy Nexus] osm0sis:
Yeah. Just defaults. If I have some time this week I'll go back a few builds to see when they changed and see if I can pick up Franco's old values for comparison. Hopefully I won't have to revert to 4.2.1. :p

If you got the permissions correct on folder (/system/etc/init.d/) and file, (rwxr-xr-x for both), then it's your ROM or another app hijacking the values later in the boot. Remove any extra init.d scripts that you don't recognize, delete/rename /system/etc/sysctl.conf, and disable any on boot stuff stuff in Settings if you're running AOKP/CM.
[Samsung Galaxy Nexus] Empty Hand:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Does the sysctl.conf script serve any purpose?
[Samsung Galaxy Nexus] osm0sis:
It lets ROM makers hijack the sysfs. ;)
[Samsung Galaxy Nexus] J-Hop2o6:
Here's another question. Do I have to edit anything inside the file for the values to stick? Or do you have it mainly "plug-n-play"?

And i'm using Xenon 6.0, which is a AOSP rom with lots of added features. And I do have sysctl, but the only things inside are: vm.dirty_ratio, vm.dirty_bg_ratio, vm.vfs_cache_pressure, vm.oom_kill_alloc_task

vm.min_free, and vm.swappiness. Not sure how those would affect the iosettings file.