lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAA25o9S=XiO7b-HNbx1GHr+ETrA_p11WU+FUprMn_VhjU=jjvw@mail.gmail.com>
Date:	Wed, 7 Nov 2012 08:40:16 -0800
From:	Luigi Semenzato <semenzato@...gle.com>
To:	Minchan Kim <minchan@...nel.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Greg KH <gregkh@...uxfoundation.org>,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org,
	Dan Magenheimer <dan.magenheimer@...cle.com>,
	Nitin Gupta <ngupta@...are.org>,
	Seth Jennings <sjenning@...ux.vnet.ibm.com>,
	Konrad Rzeszutek Wilk <konrad@...nok.org>,
	Jens Axboe <axboe@...nel.dk>,
	Pekka Enberg <penberg@...helsinki.fi>,
	gaowanlong@...fujitsu.com
Subject: Re: [PATCH v4 0/3] zram/zsmalloc promotion

Since Chrome OS was mentioned: the main reason why we don't use swap
to a disk (rotating or SSD) is because it doesn't degrade gracefully
and leads to a bad interactive experience.  Generally we prefer to
manage RAM at a higher level, by transparently killing and restarting
processes.  But we noticed that zram is fast enough to be competitive
with the latter, and it lets us make more efficient use of the
available RAM.

As Minchan said, the zram module in itself appears to work fine.  We
are hitting other mm issues (one of which was recently fixed) which
most likely are exposed by the different patterns of memory allocation
when using zram.

On Wed, Nov 7, 2012 at 2:38 AM, Minchan Kim <minchan@...nel.org> wrote:
> Hi Andrew,
>
> On Wed, Nov 7, 2012 at 8:32 AM, Andrew Morton <akpm@...ux-foundation.org>
> wrote:
>> On Fri, 2 Nov 2012 16:12:44 +0900
>> Minchan Kim <minchan@...nel.org> wrote:
>>
>>> This patchset promotes zram/zsmalloc from staging.
>>
>> The changelogs are distressingly short of *reasons* for doing this!
>>
>>> Both are very clean and zram have been used by many embedded product
>>> for a long time.
>>
>> Well that's interesting.
>>
>> Which embedded products? How are they using zram and what benefit are
>> they observing from it, in what scenarios?
>>
>
> At least, major TV companys have used zram as swap since two years ago and
> recently our production team released android smart phone with zram which is
> used as swap, too.
> And there is trial to use zram as swap in ChromeOS project, too. (Although
> they report some problem recently, it was not a problem of zram).
> When you google zram, you can find various usecase in xda-developers.
>
> With my experience, the benefit in real practice was to remove jitter of
> video application. It would be effect of efficient memory usage by
> compression but more issue is whether swap is there or not in the system. As
> you know, recent mobile platform have used JAVA so there are lots of
> anonymous pages. But embedded system normally doesn't use eMMC or SDCard as
> swap because there is wear-leveling issue and latency so we can't reclaim
> anymous pages. It sometime ends up making system very slow when it requires
> to get contiguous memory and even many file-backed pages are evicted. It's
> never what embedded people want it. Zram is one of best solution for that.
>
> It's very hard to type with mobile phone. :(
>
> --
> Kind regards,
> Minchan Kim
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ