Tim Walker <tim.t.walker@xxxxxxxxxxx> writes: > The IO Scheduler is a useful place to implement per-actuator load > management, but with the LBA-to-actuator mapping available to user > space (via sysfs) it could also be done at the user level. Or pretty > much anywhere else where we have knowledge and control of the various > streams. I suppose there may be some things user space could do with the information, but mainly doesn't it have to be done in the IO scheduler? As it stands now, it is going to try to avoid seeking between the two regions even though the drive can service a contiguous stream from both just fine, right?
