All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Wool <vitaly.wool@konsulko.com>
To: "Marcin Mirosław" <marcin@mejor.pl>
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: Tue, 2 Aug 2016 11:13:43 +0200	[thread overview]
Message-ID: <CAM4kBBL03Qi=iBo9BHfrxv8OXdpMV1DFccm+C9VF1stCTivnzg@mail.gmail.com> (raw)
In-Reply-To: <15aabbf1-4036-cd15-a593-3ebfe429e948@mejor.pl>

[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]

On Mon, Aug 1, 2016 at 11:21 AM, Marcin Mirosław <marcin@mejor.pl> wrote:

> W dniu 01.08.2016 o 11:08, Vitaly Wool pisze:
> > Hi Marcin,
> >
> > Den 1 aug. 2016 11:04 fm skrev "Marcin Mirosł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 > ...`
>

Well, first of all this is Intel right?

~vitaly

[-- Attachment #2: Type: text/html, Size: 1870 bytes --]

  reply	other threads:[~2016-08-02  9:13 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
2016-08-02  9:13     ` Vitaly Wool [this message]
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='CAM4kBBL03Qi=iBo9BHfrxv8OXdpMV1DFccm+C9VF1stCTivnzg@mail.gmail.com' \
    --to=vitaly.wool@konsulko.com \
    --cc=linux-mm@kvack.org \
    --cc=marcin@mejor.pl \
    /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.