On Mon, Sep 22, 2014 at 02:17:33PM -0700, Andrew Morton wrote:
> On Mon, 22 Sep 2014 09:03:11 +0900 Minchan Kim wrote:
>
> > Some zram usecase could want lower fullness than default 80 to
> > avoid unnecessary swapout-and-fail-recover overhead.
> >
> > A typical example is that mutliple swap
On Mon, 22 Sep 2014 09:03:11 +0900 Minchan Kim wrote:
> Some zram usecase could want lower fullness than default 80 to
> avoid unnecessary swapout-and-fail-recover overhead.
>
> A typical example is that mutliple swap with high piroirty
> zram-swap and low priority HDD-swap so it could still
On Mon, 22 Sep 2014 09:03:11 +0900 Minchan Kim minc...@kernel.org wrote:
Some zram usecase could want lower fullness than default 80 to
avoid unnecessary swapout-and-fail-recover overhead.
A typical example is that mutliple swap with high piroirty
zram-swap and low priority HDD-swap so it
On Mon, Sep 22, 2014 at 02:17:33PM -0700, Andrew Morton wrote:
On Mon, 22 Sep 2014 09:03:11 +0900 Minchan Kim minc...@kernel.org wrote:
Some zram usecase could want lower fullness than default 80 to
avoid unnecessary swapout-and-fail-recover overhead.
A typical example is that mutliple
Some zram usecase could want lower fullness than default 80 to
avoid unnecessary swapout-and-fail-recover overhead.
A typical example is that mutliple swap with high piroirty
zram-swap and low priority HDD-swap so it could still enough
free swap space although one of swap devices is full(ie,
Some zram usecase could want lower fullness than default 80 to
avoid unnecessary swapout-and-fail-recover overhead.
A typical example is that mutliple swap with high piroirty
zram-swap and low priority HDD-swap so it could still enough
free swap space although one of swap devices is full(ie,
6 matches
Mail list logo
