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: Tue, 2 Aug 2016 11:52:47 +0200 [thread overview]
Message-ID: <c3b83e70-5c41-8259-37bf-4c194bd59f4b@mejor.pl> (raw)
In-Reply-To: <CAM4kBBL03Qi=iBo9BHfrxv8OXdpMV1DFccm+C9VF1stCTivnzg@mail.gmail.com>
W dniu 02.08.2016 o 11:13, Vitaly Wool pisze:
>
>
> On Mon, Aug 1, 2016 at 11:21 AM, Marcin MirosA?aw <marcin@mejor.pl
> <mailto: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 MirosA?aw" <marcin@mejor.pl <mailto:marcin@mejor.pl>
> > <mailto: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>
> >
> <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?
Yes, this is Intel and I'm sitting inside vm (KVM).
[...]
processor : 3
vendor_id : GenuineIntel
cpu family : 6
model : 62
model name : Intel(R) Xeon(R) CPU E5-2630 v2 @ 2.60GHz
stepping : 4
microcode : 0x1
cpu MHz : 2599.851
cache size : 4096 KB
physical id : 3
siblings : 1
core id : 0
cpu cores : 1
apicid : 3
initial apicid : 3
fpu : yes
fpu_exception : yes
cpuid level : 13
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb lm
constant_tsc arch_perfmon nopl eagerfpu pni pclmulqdq ssse3 cx16 pcid
sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx f16c rdrand
hypervisor lahf_lm fsgsbase smep xsaveopt
bugs :
bogomips : 5199.99
clflush size : 64
cache_alignment : 64
address sizes : 46 bits physical, 48 bits virtual
power management:
I've got 4 VCPU.
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-02 9:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 9:03 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
2016-08-02 9:52 ` Marcin Mirosław [this message]
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=c3b83e70-5c41-8259-37bf-4c194bd59f4b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox