Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp545638pxk; Fri, 11 Sep 2020 13:53:21 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx+9LZas25r+Dfyh2DkycjLq30d//rJBUqvymHsBdnpGn1aa14APNNix4b3PIWv2bbaa+X+ X-Received: by 2002:a17:906:4e4a:: with SMTP id g10mr3641888ejw.274.1599857601636; Fri, 11 Sep 2020 13:53:21 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1599857601; cv=none; d=google.com; s=arc-20160816; b=OAMVQnArBNqVvSzLFlGwBvZRVXbRWSuugBAKG9LuFw6qJyzeZjzYbligs30G3b+brQ TX3Dn+mVxGXsKFJDMNkHd7UaOO8CuixjZP6aao5nIj31iFB0EErBeB73H9QuuvDJoVel fquuM2ssR0Q1QigPquI0puZF27B4HjRyhz2gkFWCZaI4qvt3bRmDNROQwfVqzVV+qug6 m+ZwqX+ILiio2wpmheefEKr5IQSG25xtG5ZSABlZ+6RO5w0SDtQZhOvFlGYYQn1dSnH+ W/LA49ho1WpjJtXmRuYWFneddzoiiAwQmiyQssGsbo3L/Spmiybr0RHWVu99604/9glq MhyQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:to:in-reply-to:cc:references:message-id :date:subject:mime-version:from:content-transfer-encoding :dkim-signature; bh=fPujA0Ryp4LyB06UqeSBwSR2AMMizIQ9L2dC6UhUTSU=; b=ky7bUBOieDbIYAaMPbhsjJP4rrntN55SkKZj96GeoV81r32NyntejEl/vWaqeH4VAd r8JEeOtU8pU6A0ajhDSi0QtcKV2l9UpUrJWTT6vNuqnOIDvmCv+OiOY/9glYPNUycvPd ZrM89DUkNIVkLZQ/QLxSowMhCWwhyAhyHQ9k5at19dZs/ZFJdNjvDGpI7UYhfwDCwoo+ 9MXhsdiksA+hIsEKXfvonkbjEA2OAqTHDbU6DXBshzmCcMMJvKVBstIbHge2ImFp82YU KmjsT9kf6Y+q+6rjE7vr72U4ZtN4ieTBCI+QQzWPqfkZT/F/eOm97oUOu3xT6CXEoSXZ FyoQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=DxsQs+vr; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id do18si2157349ejc.13.2020.09.11.13.52.58; Fri, 11 Sep 2020 13:53:21 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=DxsQs+vr; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725835AbgIKUtT (ORCPT + 99 others); Fri, 11 Sep 2020 16:49:19 -0400 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:22838 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725803AbgIKUtN (ORCPT ); Fri, 11 Sep 2020 16:49:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1599857351; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=fPujA0Ryp4LyB06UqeSBwSR2AMMizIQ9L2dC6UhUTSU=; b=DxsQs+vrsh6N48NSsLIzNV/crBN+12ZbSE5PYcxLHb47GRJCWFlV5D/ivkSUWralTJhUcD P1ZNbBV+SnMGnlnFl7Nvx1S0qRSTY2gkfl5cW0g7zYQeH1I8TUp+mGLGqL3xtqjx2iv6S1 SwZgWdcSJ/yjTFZtjRvqHboxUge/C+I= Received: from mail-ed1-f70.google.com (mail-ed1-f70.google.com [209.85.208.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-299-76UNC8PpNgmj0Ss0wfeGfw-1; Fri, 11 Sep 2020 16:49:09 -0400 X-MC-Unique: 76UNC8PpNgmj0Ss0wfeGfw-1 Received: by mail-ed1-f70.google.com with SMTP id n4so5529300edo.20 for ; Fri, 11 Sep 2020 13:49:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=fPujA0Ryp4LyB06UqeSBwSR2AMMizIQ9L2dC6UhUTSU=; b=ANwh7zUH7eALnr7Q+gurSd+y4KGw8DkO6/iMQnntBYDgPuMC72TB6IXoqbOLRVHuVF vnk3Y/38JgHQeme2AD9sg9FpNVE3WooYVFNoTd689izFqmzyKF9DZhyul6Cf4lizV/ia gdXuW0qKEv+a5oOTba83nUQiIWXnopVUt1tYrlmpdpijB1LnBrU7NMvPCOmffMq89alD 8jDsOm+34gpZUeoQywfgIUnKT9ZNSGbLZOAcj4tUF92vSdpMNH21z9As7c3s0Z6LGAjb Lq0HcufBrNcNx709WfHBuh2S9aRkY6UacBf0kL7yg5rTXDe1E2sQY2J+adSr4OmgwoaE 1j1A== X-Gm-Message-State: AOAM533t3u3VDAOqOhBOvB8VzBELeLV8wbCqX0DY9dcNOiqYpVH4pmJD T6qNLTFh6tL6Lnc/PTtscMTVkGma6LFtz9bbwvro+zUdpxNwjWtVYseMeqXsdJGsv5IuCftJa+M 3S2xQQHyfiIAZMwKWYrHdmZw1 X-Received: by 2002:aa7:de91:: with SMTP id j17mr4457858edv.85.1599857348683; Fri, 11 Sep 2020 13:49:08 -0700 (PDT) X-Received: by 2002:aa7:de91:: with SMTP id j17mr4457832edv.85.1599857348528; Fri, 11 Sep 2020 13:49:08 -0700 (PDT) Received: from [192.168.3.122] (p5b0c6263.dip0.t-ipconnect.de. [91.12.98.99]) by smtp.gmail.com with ESMTPSA id g20sm2586507edh.62.2020.09.11.13.49.07 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 11 Sep 2020 13:49:07 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: David Hildenbrand Mime-Version: 1.0 (1.0) Subject: Re: Ways to deprecate /sys/devices/system/memory/memoryX/phys_device ? Date: Fri, 11 Sep 2020 22:49:06 +0200 Message-Id: <00BF194F-9B67-4F7B-AA6F-902E2BCB2F7B@redhat.com> References: <64ad68af6abe4d6b9a346e777e2bd864@intel.com> Cc: David Hildenbrand , "Hansen, Dave" , Michal Hocko , Gerald Schaefer , "akpm@linux-foundation.org" , Greg KH , =?utf-8?Q?Jan_H=C3=B6ppner?= , Heiko Carstens , "linux-mm@kvack.org" , "linux-api@vger.kernel.org" , Dave Hansen , "linux-kernel@vger.kernel.org" In-Reply-To: <64ad68af6abe4d6b9a346e777e2bd864@intel.com> To: "Luck, Tony" X-Mailer: iPhone Mail (17G68) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Am 11.09.2020 um 22:09 schrieb Luck, Tony : >=20 > =EF=BB=BF >>=20 >> How would it behave after hotplugging a single DIMM - I assume a single p= age will only be mapped to that DIMM (otherwise a lot of stuff would habe to= be moved around. Would the mapping change after a reboot - especially can a= DIMM that could get hotunplugged before suddenly no longer be hotunplugged i= ndividually? >=20 >=20 > We don't currently have any platforms that would allow hot adding at the D= IMM level. > The Brickland generation of E7 Xeon servers (Ivybridge, Haswell, Broadwell= ) allowed > for hot plugging a riser card that contained up to 12 DIMMs. >=20 > If you did add memory it would have to appear at the top of the system phy= sical > address space. No interleave (unless you added more than one DIMM in a sin= gle > operation). After a reboot the system would likely shuffle things around t= o and > interleave. >=20 Thanks a lot - so I=E2=80=98m really spoiled by hot(un)plug capabilities in v= irtualized environments :D > -Tony