From: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
To: Vitaly Wool <vitalywool@gmail.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Minchan Kim <minchan@kernel.org>,
Seth Jennings <sjennings@variantweb.net>,
Dan Streetman <ddstreet@ieee.org>,
Andrew Morton <akpm@linux-foundation.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>
Subject: Re: [PATCH v2] zbud: allow up to PAGE_SIZE allocations
Date: Fri, 25 Sep 2015 18:57:02 +0900 [thread overview]
Message-ID: <20150925095702.GA1049@swordfish> (raw)
In-Reply-To: <CAMJBoFPg+rZqXRdJCLK1RYY8vs0NmBZzuTUD33AMzQn+tyN5Jw@mail.gmail.com>
On (09/25/15 10:27), Vitaly Wool wrote:
> > Have you seen those symptoms before? How did you come up to a conclusion
> > that zram->zbud will do the trick?
>
> I have data from various tests (partially described here:
> https://lkml.org/lkml/2015/9/17/244) and once again, I'll post a reply
yeah, I guess I'm just not so bright to quickly understand what is wrong
with zsmalloc from those numbers.
> to https://lkml.org/lkml/2015/9/15/33 with more detailed test
> description and explanation why zsmalloc is not the right choice for
> me.
great, thanks.
> > If those symptoms are some sort of a recent addition, then does it help
> > when you disable zsmalloc compaction?
>
> No it doesn't. OTOH enabled zsmalloc compaction doesn't seem to have a
> substantial effect either.
hm. ok, that was my quick guess.
-ss
--
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:[~2015-09-25 9:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-22 12:17 [PATCH v2] zbud: allow up to PAGE_SIZE allocations Vitaly Wool
2015-09-22 21:49 ` Dan Streetman
2015-09-23 8:07 ` Vitaly Wool
2015-09-23 20:59 ` Vitaly Wool
2015-09-23 22:41 ` Seth Jennings
2015-09-25 5:56 ` Vitaly Wool
2015-09-23 3:18 ` Seth Jennings
2015-09-23 7:54 ` Vitaly Wool
2015-09-23 21:57 ` Seth Jennings
2015-09-25 2:13 ` Minchan Kim
2015-09-25 8:05 ` Sergey Senozhatsky
2015-09-25 8:27 ` Vitaly Wool
2015-09-25 9:57 ` Sergey Senozhatsky [this message]
2015-09-25 8:17 ` Vitaly Wool
2015-09-25 8:47 ` Minchan Kim
2015-09-25 8:50 ` Minchan Kim
2015-09-25 10:51 ` Vitaly Wool
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=20150925095702.GA1049@swordfish \
--to=sergey.senozhatsky@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ddstreet@ieee.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sjennings@variantweb.net \
--cc=vitalywool@gmail.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;
as well as URLs for NNTP newsgroup(s).