On Wed, Oct 15, 2014 at 11:56:33PM -0600, Justin T. Gibbs wrote:
> avg pointed out the rate limiting code in vm_pageout_scan() during discussion
> about PR 187594. While it certainly can contribute to the problems discussed
> in that PR, a bigger problem is that it can allow the OOM killer to be
On 16/10/2014 12:08, Steven Hartland wrote:
> Unfortunately ZFS doesn't prevent new inflight writes until it
> hits zfs_dirty_data_max, so while what your suggesting will
> help, if the writes come in quick enough I would expect it to
> still be able to out run the pageout.
As I've mentioned, arc_
quot;
To:
Cc: ; "Andriy Gapon"
Sent: Thursday, October 16, 2014 6:56 AM
Subject: OOM killer and kernel cache reclamation rate limit in vm_pageout_scan()
avg pointed out the rate limiting code in vm_pageout_scan() during discussion about PR 187594. While it certainly can contribute to
the p
On 16/10/2014 08:56, Justin T. Gibbs wrote:
> avg pointed out the rate limiting code in vm_pageout_scan() during discussion
> about PR 187594. While it certainly can contribute to the problems discussed
> in that PR, a bigger problem is that it can allow the OOM killer to be
> triggered even thoug
On 16/10/2014 08:56, Justin T. Gibbs wrote:
> avg pointed out the rate limiting code in vm_pageout_scan() during discussion
> about PR 187594. While it certainly can contribute to the problems discussed
> in that PR, a bigger problem is that it can allow the OOM killer to be
> triggered even thoug
avg pointed out the rate limiting code in vm_pageout_scan() during discussion
about PR 187594. While it certainly can contribute to the problems discussed
in that PR, a bigger problem is that it can allow the OOM killer to be
triggered even though there is plenty of reclaimable memory available
