From: Luigi Semenzato <semenzato@google.com>
To: Seth Jennings <sjennings@variantweb.net>
Cc: linux-mm@kvack.org, Minchan Kim <minchan@kernel.org>,
Slava Malyugin <slavamn@google.com>,
Sonny Rao <sonnyrao@google.com>
Subject: Re: compaction of zspages
Date: Wed, 27 Aug 2014 16:25:52 -0700 [thread overview]
Message-ID: <CAA25o9RVZGqZTBM6+sPXBfMB_b5ZHCjPWwdWVy_cB0_whiiQrw@mail.gmail.com> (raw)
In-Reply-To: <20140827220955.GA26902@cerebellum.variantweb.net>
Thank you Seth!
On Wed, Aug 27, 2014 at 3:09 PM, Seth Jennings <sjennings@variantweb.net> wrote:
> On Wed, Aug 27, 2014 at 02:42:52PM -0700, Luigi Semenzato wrote:
>> Hello Minchan and others,
>>
>> I just noticed that the data structures used by zsmalloc have the
>> potential to tie up memory unnecessarily. I don't call it "leaking"
>> because that memory can be reused, but it's not necessarily returned
>> to the system upon freeing.
>
> Yes, this is a known condition in zsmalloc.
>
> Compaction is not a simple as it seems because zsmalloc returns a handle
> to the user that encodes the pfn. In order the implement a compaction
> system, there would need to be some notification method to the alert the
> user that their allocation has moved and provide a new handle so the
> user can update its structures. This is very non-trivial and I'm not
> sure that it can be done safely (i.e. without races).
Since the handles are opaque, we can add a level of indirection
without affecting users. Assuming that the overhead is tolerable, or
anyway less than what we're wasting now. (For some definition of
"less".)
I agree that notification + update would be a huge pain, not really acceptable.
>
> I looked at it a while back and it would be a significant effort.
>
> And yes, if you could do such a thing, you would not want the compaction
> triggered by the shrinkers as the users of zsmalloc are only active
> under memory pressure. Something like a periodic compaction kthread
> would be the best way (after two minutes of thinking about it).
>
> Seth
>
>
>>
>> I have no idea if this has any impact in practice, but I plan to run a
>> test in the near future. Also, I am not sure that doing compaction in
>> the shrinkers (as planned according to a comment) is the best
>> approach, because the shrinkers won't be called unless there is
>> considerable pressure, but the compaction would be more effective when
>> there is less pressure.
>>
>> Some more detail here:
>>
>> https://code.google.com/p/chromium/issues/detail?id=408221
>>
>> Should I open a bug on some other tracker?
>>
>> Thank you very much!
>> Luigi
>>
>> --
>> To unsubscribe, send a message with 'unsubscribe linux-mm' in
>> the body to majordomo@kvack.org. For more info on Linux MM,
>> see: http://www.linux-mm.org/ .
>> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-08-27 23:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 21:42 Luigi Semenzato
[not found] ` <20140827220955.GA26902@cerebellum.variantweb.net>
2014-08-27 23:25 ` Luigi Semenzato [this message]
2014-08-28 0:17 ` Minchan Kim
2014-08-28 0:27 ` Luigi Semenzato
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA25o9RVZGqZTBM6+sPXBfMB_b5ZHCjPWwdWVy_cB0_whiiQrw@mail.gmail.com \
--to=semenzato@google.com \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=sjennings@variantweb.net \
--cc=slavamn@google.com \
--cc=sonnyrao@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox