[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4f986c65-c17e-47d8-9c30-60cd17809cbb@default>
Date: Mon, 19 Jul 2010 12:57:24 -0700 (PDT)
From: Dan Magenheimer <dan.magenheimer@...cle.com>
To: Nitin Gupta <ngupta@...are.org>,
Pekka Enberg <penberg@...helsinki.fi>,
Hugh Dickins <hugh.dickins@...cali.co.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
Greg KH <greg@...ah.com>, Rik van Riel <riel@...hat.com>,
Avi Kivity <avi@...hat.com>,
Christoph Hellwig <hch@...radead.org>,
Minchan Kim <minchan.kim@...il.com>,
Konrad Wilk <konrad.wilk@...cle.com>
Cc: linux-mm <linux-mm@...ck.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH 0/8] zcache: page cache compression support
> We only keep pages that compress to PAGE_SIZE/2 or less. Compressed
> chunks are
> stored using xvmalloc memory allocator which is already being used by
> zram
> driver for the same purpose. Zero-filled pages are checked and no
> memory is
> allocated for them.
I'm curious about this policy choice. I can see why one
would want to ensure that the average page is compressed
to less than PAGE_SIZE/2, and preferably PAGE_SIZE/2
minus the overhead of the data structures necessary to
track the page. And I see that this makes no difference
when the reclamation algorithm is random (as it is for
now). But once there is some better reclamation logic,
I'd hope that this compression factor restriction would
be lifted and replaced with something much higher. IIRC,
compression is much more expensive than decompression
so there's no CPU-overhead argument here either,
correct?
Thanks,
Dan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists