> > but that sure looks like the low hanging fruit.
> It's low alright. AFAIK Linux has always had this problem of
> seizing up when there's a lot of dirty data around.
Somehow I doubt the "seizing up" problem is caused by too much
scanning. In fact, I'm pretty convinced it is caused by having
too much IO submitted at once (and stalling in __get_request_wait).
The scanning is probably not relevant at all and it may be
beneficial to just ignore the scanning for now and do our best
to keep the pages in better LRU order.
-- Bravely reimplemented by the knights who say "NIH".
Spamtraps of the month: email@example.com firstname.lastname@example.org
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/