Re: Massive interactivity improvement under high I/O load!
 

Yes, as I understand it, that's exactly why. Run "ls" on the "/sys/block" directory. If there's no mmcblk1 folder in there, then your device just doesn't see that piece of hardware - not having it in there at all being a logical reason for it not being able to see it.

Re: Massive interactivity improvement under high I/O load!
 

Do you know what the MMC-driver actually does? It appears to simply make the device unavailable without unmounting it, but appearances can be deceiving so maybe it does more than that.

And when you say ruin, do you mean simply corrupt the data on it by not leaving it in a clean state or do you mean electrically damage so it can't be used again? If you just mean might corrupt the data on the card, I don't see how the driver removing the device without unmounting the filesystem is any better than yanking the card.

Re: Massive interactivity improvement under high I/O load!
 

(Typing this on the FastSMSEvo keyboard in portrait mode - N900 sure has come far with so little manufacturer support.) Anyway, I'm pretty certain it unmounts it. Simply making the card/MyDocs unaccessible would be useless for the only reason that's even implemented - making sure the file systems/partitions don't get raped. Nokia execs might be stupid but their programmers aren't, mostly.

And, yes, were talking about corruption digitally, not physical damage.

So yes, that is different than making the cards inaccessible. (If cards were inaccessible but mounted, I'm pretty sure it would mess up your storage just about every time you used Mass Storage mode, without jumping through way too many hoops. Just a guess though, I am by no means an expert.)

Re: Massive interactivity improvement under high I/O load!
 

I mean electrical (or lowest level logical) damage caused by breaking power supply so a erase or flash cycle gets aborted. (possible) Result: card defect, bin it.

/j

Re: Massive interactivity improvement under high I/O load!
 

Not sure on the SLUB/SLAB/SLOB/SLQB argument, but ramzez is basically just a port of compcache. I've tried to incorporate it into the BFS kernel, but Nokia screwed around so much with the swapping code (to try to align pages) that unfortunately it's unstable, especially with the swap notify patch (even when I modified it to try to allow for their swap_remap nonsense). This can be shown up very easily by simply running two memhog's of around 200MiB at the same time - OOM is the usual result, with the occasional complete system crash. Lovely..

Re: Massive interactivity improvement under high I/O load!
 

Thanks, then I guess if the driver cuts power to the slot what it does makes sense.

Re: Massive interactivity improvement under high I/O load!
 

By the way, I meant to mention but didn't have much time to post; there is also an anti-stalling I/O patch which I successfully compiled into the BFS kernel - it's on the garage page now, although disabled by default:

https://garage.maemo.org/tracker/ind...1528&atid=5523

It should also be trivial to patch into kernel-power, if anyone is so inclined..

Re: Massive interactivity improvement under high I/O load!
 

Just out of curiosity, have you tried running that memhog test with more min_free_kbytes?

Re: Massive interactivity improvement under high I/O load!
 

Yeah me too. Still would like to figure out a way to throw it all onto a bigger display, somehow...

http://farm5.static.flickr.com/4091/...d13fe967_m.jpg

Re: Massive interactivity improvement under high I/O load!
 

I've tried this:

echo 4 > /sys/block/mmcblk0/queue/nr_requests
echo 200 > /proc/sys/vm/vfs_cache_pressure

from ur setting and it seems to me an improvment.

before i did this:

echo 4000 > /sys/block/mmcblk0/queue/nr_requests.

But I have this

echo 1250 > /proc/sys/vm/dirty_writeback_centisecs
echo 1250 > /proc/sys/vm/dirty_expire_centisecs

and

usr/bin/read-ahead /dev/mmcblk0p1 4000

and also i enabled

echo 1 > /proc/sys/kernel/sched_compat_yield

which i found a huge improvement.

I have compiled read-ahead myself. what do u think? did u tried my tools? did u ran bonnie++ before and after ur optimization? i did but i forgot the result. Anyway thank u for sharing i got a hard time with this device!