> Today's patch tackles the use-once problem, that is, the problem of
> how to identify and discard pages containing data likely to be used
> only once in a long time, while retaining pages that are used more
> often.
>
> I'll try to explain not only what I did, but the process I went
> through to arrive at this particular approach. This requires some
> background.
Well, as I see the patch should remove the problem where drop_behind()
deactivates pages of a readahead window even if some of those pages are
not "used-once" pages, right ?
I just want to make sure the performance improvements you're seeing caused
by the fix of this _particular_ problem.
If we knew the amount of non-used-once pages which drop_behind() is
deactivating under _your_ tests, we could make absolute sure about the
problem.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/