On Fri, Apr 27 2007, Linus Torvalds wrote:
> So I do believe that we could probably do something about the IO
> scheduling _too_:
>
> - break up large write requests (yeah, it will make for worse IO
> throughput, but if make it configurable, and especially with
> controllers that don't have insane overheads per command, the
> difference between 128kB requests and 16MB requests is probably not
> really even noticeable - SCSI things with large per-command overheads
> are just stupid)
>
> Generating huge requests will automatically mean that they are
> "unbreakable" from an IO scheduler perspective, so it's bad for latency
> for other reqeusts once they've started.
Overlooked this one initially... We actually don't generate huge
requests, exactly because of that. Even if the device can do large
requests (most SATA disks today can do 32meg), we default to 512kB as
the largest one that we will build due to file system requests. It's
trivial to reduce that limit, see /sys/block/<dev>/queue/max_sectors_kb.
That controls the maximum per-request size.
--
Jens Axboe
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
