[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170601064954.GB7593@osiris>
Date: Thu, 1 Jun 2017 08:49:54 +0200
From: Heiko Carstens <heiko.carstens@...ibm.com>
To: Michal Hocko <mhocko@...nel.org>
Cc: Gerald Schaefer <gerald.schaefer@...ibm.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [-next] memory hotplug regression
On Wed, May 31, 2017 at 08:24:40AM +0200, Michal Hocko wrote:
> > # cat /sys/devices/system/memory/memory16/valid_zones
> > Normal Movable
> > # echo online_movable > /sys/devices/system/memory/memory16/state
> > # cat /sys/devices/system/memory/memory16/valid_zones
> > Movable
> > # cat /sys/devices/system/memory/memory18/valid_zones
> > Movable
> > # echo online > /sys/devices/system/memory/memory18/state
> > # cat /sys/devices/system/memory/memory18/valid_zones
> > Normal <--- should be Movable
> > # cat /sys/devices/system/memory/memory17/valid_zones
> > <--- no output
>
> OK, so this is an independent problem and an unrelated one to the
> patch I've posted. We need two patches actually. Damn, I hate
> MMOP_ONLINE_KEEP. I will send 2 patches as a reply to this email.
Tested with your patches on top of linux-next as of yesterday, however
starting at commit fa812e869a6fe7495a17150bb2639075081ef709 ("mm/zswap.c:
delete an error message for a failed memory allocation in
zswap_dstmem_prepare()"), since the "mm: per-lruvec slab stats" patch
series breaks everything ;)
Tested-by: Heiko Carstens <heiko.carstens@...ibm.com>
Powered by blists - more mailing lists