On Thursday June 1, [email protected] wrote:
>
> I keep telling you. Put the unplug after submission of IO. Not before
> waiting for IO.
>
> I'll give you one example of how it could be better (feel free to ask
> for others too). Your sys_readahead(). Someone asks to readahead 1MB
> of data, currently if the queue is empty, that's going to sit around
> for 4ms before starting the read. 4ms later, the app comes back hoping
> for the request to have finished. Unfortunately it takes another 4ms.
> Throughput is halved.
I think this is all a question of heuristics. There is a trade off
between throughput and latency, and making the right decisions require
prescience, and I don't think either Intel or AMD have implemented
yet.
One could argue that the best you can get would involve making
decisions at the lowest level - where device characteristics are
known - and using hints from upper levels like "I'm going to submit
lots of requests now" and "Ok, I'm done" and "I want this page NOW".
These should be hints and the device can treat them as it likes.
Maybe a disk device could estimate the time it would take to process
the current plugged queue, and if the first request were older than
half that time, unplug the queue, unless there was a genuine
expectation of more requests very soon...
Currently the decisions are made at a reasonably low level, but the
only hint is "I want some page somewhere on this device now, or maybe
I just want to stop anyone changing ->mapping", which is a fairly
broad and inaccurate hint....
But the real point is that as this is an heuristic, it is very hard to
argue in the abstract about what is best. We really need measurements
to show that changes to have a measurable effect.
I have an interesting issue with plugging and raid5 at the moment. As
I mentioned earlier, plugging only affects incomplete stripes being
written. So if a very long, totally sequential write is being issued
(dd of=/dev/md0) then we never really need to unplug (except may at
the end). But unplugging does happen (3msec timeout at least) and so
we sometimes end up pre-reading for partial stripes even though there
is really no need.
What I would really like is for ->unplug_fn to know something about
why it is being called.
- if it is for read, I'll unplug component devices, but not
incomplete writes.
- if it is for write, I'll unplug writes, but I'd really rather
know which address was required
- if it is a timeout, I'll unplug writes that have been pending
for more than 2msec.
I suspect there is at least one workload that this would help, but I
would need to measure to be sure.
... maybe I'll try adding a 'how' option to ->unplug_fn and see what I
can come up with...
NeilBrown
-
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]
