|
Small feature request
Hi again, Steven!
I wonder if it would hurt if I asked for BLK_DEV_IO_TRACE on the next build? I don't think it would hurt performance since it is disabled by default. Either blktrace can enable that or the user through /sys/block/sda/sda1/trace/enable. I'm a system monitoring freak, so that'd be awesome to have on every release! Please? If not enabled in the kernel, the user will see: :: Code :: (teresaejunior)> sudo blktrace /dev/sda1
BLKTRACESETUP(2) /dev/sda1 failed: 25/Inappropriate ioctl for device Thread 0 failed open /sys/kernel/debug/block/(null)/trace0: 2/No such file or directory Thread 1 failed open /sys/kernel/debug/block/(null)/trace1: 2/No such file or directory FAILED to start thread on CPU 0: 1/Operation not permitted FAILED to start thread on CPU 1: 1/Operation not permitted Back to top |
|||||
|
Hmm, that looks interesting. IO is historically the most frustrating bottleneck for desktops. It would be nice to know what your system is doing when it's stalled with the hard drive light blinking frantically.
The IO subsystem in linux seems to be pretty far away from the other core subsystems that are more cpu intensive (mm, cpu scheduling), so it should be pretty benign if left disabled for people who don't care. I'll take a look for the 3.9 series. Back to top |
|||||
|
Thanks so much :)
Back to top |
|||||
|
All times are GMT - 8 Hours
|
|||||