From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752093AbdB0LZe (ORCPT ); Mon, 27 Feb 2017 06:25:34 -0500 Received: from mx0a-001b2d01.pphosted.com ([148.163.156.1]:58002 "EHLO mx0a-001b2d01.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752047AbdB0LZc (ORCPT ); Mon, 27 Feb 2017 06:25:32 -0500 Date: Mon, 27 Feb 2017 12:25:10 +0100 From: Heiko Carstens To: Vitaly Kuznetsov Cc: Michal Hocko , linux-mm@kvack.org, Andrew Morton , Greg KH , "K. Y. Srinivasan" , David Rientjes , Daniel Kiper , linux-api@vger.kernel.org, LKML , linux-s390@vger.kernel.org, xen-devel@lists.xenproject.org, linux-acpi@vger.kernel.org, Michal Hocko Subject: Re: [RFC PATCH] mm, hotplug: get rid of auto_online_blocks References: <20170227092817.23571-1-mhocko@kernel.org> <87lgssvtni.fsf@vitty.brq.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87lgssvtni.fsf@vitty.brq.redhat.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-TM-AS-GCONF: 00 X-Content-Scanned: Fidelis XPS MAILER x-cbid: 17022711-0040-0000-0000-000003330DE0 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 17022711-0041-0000-0000-0000244D78FD Message-Id: <20170227112510.GA4129@osiris> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2017-02-27_08:,, signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1612050000 definitions=main-1702270116 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 27, 2017 at 11:02:09AM +0100, Vitaly Kuznetsov wrote: > A couple of other thoughts: > 1) Having all newly added memory online ASAP is probably what people > want for all virtual machines. This is not true for s390. On s390 we have "standby" memory that a guest sees and potentially may use if it sets it online. Every guest that sets memory offline contributes to the hypervisor's standby memory pool, while onlining standby memory takes memory away from the standby pool. The use-case is that a system administrator in advance knows the maximum size a guest will ever have and also defines how much memory should be used at boot time. The difference is standby memory. Auto-onlining of standby memory is the last thing we want. > Unfortunately, we have additional complexity with memory zones > (ZONE_NORMAL, ZONE_MOVABLE) and in some cases manual intervention is > required. Especially, when further unplug is expected. This also is a reason why auto-onlining doesn't seem be the best way.