From: "Marcin Mirosław" <marcin@mejor.pl>
To: Vitaly Wool <vitaly.wool@konsulko.com>
Cc: Linux-MM <linux-mm@kvack.org>
Subject: Re: Choosing z3fold allocator in zswap gives WARNING: CPU: 0 PID: 5140 at mm/zswap.c:503 __zswap_pool_current+0x56/0x60
Date: Mon, 1 Aug 2016 11:21:11 +0200 [thread overview]
Message-ID: <15aabbf1-4036-cd15-a593-3ebfe429e948@mejor.pl> (raw)
In-Reply-To: <CAM4kBBLsK99PXaCa8Po3huOyGx+qHTrq3Vgsh+FoqqRaMLv-vQ@mail.gmail.com>
W dniu 01.08.2016 o 11:08, Vitaly Wool pisze:
> Hi Marcin,
>
> Den 1 aug. 2016 11:04 fm skrev "Marcin MirosA?aw" <marcin@mejor.pl
> <mailto:marcin@mejor.pl>>:
>>
>> Hi!
>> I'm testing kernel-git
>> (git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> <http://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git> , at
>> 07f00f06ba9a5533d6650d46d3e938f6cbeee97e ) because I noticed strange OOM
>> behavior in kernel 4.7.0. As for now I can't reproduce problems with
>> OOM, probably it's fixed now.
>> But now I wanted to try z3fold with zswap. When I did `echo z3fold >
>> /sys/module/zswap/parameters/zpool` I got trace from dmesg:
>
> Could you please give more info on how to reproduce this?
Nothing special. Just rebooted server (vm on kvm), started services and
issued `echo z3fold > ...`
Marcin
--
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:[~2016-08-01 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 9:03 Choosing z3fold allocator in zswap gives WARNING: CPU: 0 PID: 5140 at mm/zswap.c:503 __zswap_pool_current+0x56/0x60 Marcin Mirosław
2016-08-01 9:08 ` Vitaly Wool
2016-08-01 9:21 ` Marcin Mirosław [this message]
2016-08-02 9:13 ` Vitaly Wool
2016-08-02 9:52 ` Marcin Mirosław
2016-08-04 11:58 ` Sergey Senozhatsky
2016-08-04 18:15 ` Dan Streetman
2016-08-05 0:43 ` Sergey Senozhatsky
2016-08-05 1:22 ` Sergey Senozhatsky
2016-08-07 22:40 ` 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=15aabbf1-4036-cd15-a593-3ebfe429e948@mejor.pl \
--to=marcin@mejor.pl \
--cc=linux-mm@kvack.org \
--cc=vitaly.wool@konsulko.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.