From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.9 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id DBA8EC43461 for ; Fri, 11 Sep 2020 20:49:14 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 5483722207 for ; Fri, 11 Sep 2020 20:49:14 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="QJhxa3rr" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 5483722207 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id A6E1E6B0002; Fri, 11 Sep 2020 16:49:13 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id A1F6A6B0003; Fri, 11 Sep 2020 16:49:13 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 90DED6B0037; Fri, 11 Sep 2020 16:49:13 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0181.hostedemail.com [216.40.44.181]) by kanga.kvack.org (Postfix) with ESMTP id 7BFBD6B0002 for ; Fri, 11 Sep 2020 16:49:13 -0400 (EDT) Received: from smtpin12.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with ESMTP id 40BB72493 for ; Fri, 11 Sep 2020 20:49:13 +0000 (UTC) X-FDA: 77251970586.12.stage56_5015162270f1 Received: from filter.hostedemail.com (10.5.16.251.rfc1918.com [10.5.16.251]) by smtpin12.hostedemail.com (Postfix) with ESMTP id 161C518021485 for ; Fri, 11 Sep 2020 20:49:13 +0000 (UTC) X-HE-Tag: stage56_5015162270f1 X-Filterd-Recvd-Size: 5103 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) by imf04.hostedemail.com (Postfix) with ESMTP for ; Fri, 11 Sep 2020 20:49:12 +0000 (UTC) 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=tCl92/mdH74jo62STODHKLgM70oNFxWq7PXsVH08St4=; b=QJhxa3rrunocPB9CyyBrHWardaokFOzeTnhJMe3ZdYWMcmP6oAGRQ8gsm/aQH1A6/6iGQA pgUr4U9RbP1g84ANRfxiXYndANDEjBLQ1zqUan1ynfjdal6YHjVne5N8RaojKqQ2pP8TiX b3lMCy51bOqTqy1tf/b5HYeVbATDpVs= Received: from mail-ed1-f71.google.com (mail-ed1-f71.google.com [209.85.208.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-108-7wVOEyyROUKB9JugmZyVAg-1; Fri, 11 Sep 2020 16:49:09 -0400 X-MC-Unique: 7wVOEyyROUKB9JugmZyVAg-1 Received: by mail-ed1-f71.google.com with SMTP id d27so5463876edj.21 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=nbhtV1Bhbdo0sTPcZMiuL8HDbQhSvO0yqjToZ2JokEJHnwJYXZM0xUg1ZhJNIGVwjM WJ4hpfcTLQxNgTYhRfC5L5HqorQ9Y+mEV/G6tBvh8z5BohXS2YE4gnuAMdTeGR8sjs8p h1IpnAQm9dn57VyxT9CBaFi5J3MWvRGR7hMmJzDTXyD/CqUNd6pVCrz7Six3F0xM8Nm+ enozg6roSR2T4om6TuaOKoNWRNtZnRJSQPX8yyrZxame1ydDODepFpPPpmD7oH+HlEtd fEM85yBCBTk9+OSNhnCKKnlYPlrJIJyf8xW1ILjulDAwxg7CYffUD22l1R9RAZqiFk3E XluA== X-Gm-Message-State: AOAM53052R4VMJ2oAXbwrOjH5TjgKPiwDTPAfcP1low7yH5KXZ9yuGU2 lox1aSMBlfalmIaCTouW8+32GmNcKnPsp5GSKwaGvv8nvATQLAJbD/bYyrahWdGYu6uXYhwwp+U aEphTPVLfCRg= X-Received: by 2002:aa7:de91:: with SMTP id j17mr4457862edv.85.1599857348713; Fri, 11 Sep 2020 13:49:08 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzE+jQqynUXOKtrNfjmqrI4QDMcdgn1AqBUZfu/2O5MLQVff4P6n5KhdEGMOOZwYcbrX5uJdQ== 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) 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) Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=david@redhat.com X-Mimecast-Spam-Score: 0.502 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 161C518021485 X-Spamd-Result: default: False [0.00 / 100.00] X-Rspamd-Server: rspam02 X-Bogosity: Ham, tests=bogofilter, spamicity=0.001098, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: > 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= page 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 c= an a DIMM that could get hotunplugged before suddenly no longer be hotunplu= gged individually? >=20 >=20 > We don't currently have any platforms that would allow hot adding at the = DIMM level. > The Brickland generation of E7 Xeon servers (Ivybridge, Haswell, Broadwel= l) 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 ph= ysical > address space. No interleave (unless you added more than one DIMM in a si= ngle > operation). After a reboot the system would likely shuffle things around= to and > interleave. >=20 Thanks a lot - so I=E2=80=98m really spoiled by hot(un)plug capabilities in= virtualized environments :D > -Tony