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 Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id E82CFC25B10 for ; Mon, 13 May 2024 09:43:16 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 48FC46B0287; Mon, 13 May 2024 05:43:16 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 41AA96B0288; Mon, 13 May 2024 05:43:16 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 291FF6B0289; Mon, 13 May 2024 05:43:16 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0013.hostedemail.com [216.40.44.13]) by kanga.kvack.org (Postfix) with ESMTP id 0B1546B0287 for ; Mon, 13 May 2024 05:43:16 -0400 (EDT) Received: from smtpin11.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay01.hostedemail.com (Postfix) with ESMTP id 708B31C12FB for ; Mon, 13 May 2024 09:43:15 +0000 (UTC) X-FDA: 82112884350.11.1602BEA Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.223.130]) by imf20.hostedemail.com (Postfix) with ESMTP id 362951C0005 for ; Mon, 13 May 2024 09:43:12 +0000 (UTC) Authentication-Results: imf20.hostedemail.com; dkim=pass header.d=suse.de header.s=susede2_rsa header.b=TStHlt6l; dkim=pass header.d=suse.de header.s=susede2_ed25519 header.b=jaU7pyWL; dkim=pass header.d=suse.de header.s=susede2_rsa header.b=TStHlt6l; dkim=pass header.d=suse.de header.s=susede2_ed25519 header.b=jaU7pyWL; spf=pass (imf20.hostedemail.com: domain of osalvador@suse.de designates 195.135.223.130 as permitted sender) smtp.mailfrom=osalvador@suse.de; dmarc=pass (policy=none) header.from=suse.de ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1715593393; h=from:from:sender: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: in-reply-to:in-reply-to:references:references:dkim-signature; bh=eCSaTwJWQtt3po9aVko9wqjZnxBfrkocdLOkhoLOyaY=; b=jb+kr7LdeEKzrQuCA/DETIpowkh1gLya3yDNaDrpj8I/L7b+rm7A7ZzX+BiX8ABOUjvA8M Q88bXAn0ZqOjOrL4Cx7MYyEkpgkJm6MuxodBVwiJT8mi1aZPm4vA6KjOYBA2AxsGt0/Owp nqgzS0dFo9YmfHlySohXqjfDgzQf+Fk= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1715593393; a=rsa-sha256; cv=none; b=POB+LnFxJScZRp4MH+6+Q6Ut+cVsU4792hQr77HSjwTMYfdwddr+ggQLBctsHMk79MWNsb ntiF2dvPiquesSiY1TptAUtq3DEGciMMwK08CXm1FAZK7SDPKLcGpXSep5Bh+EjuStDCH8 WGU1Opl3pGhPEEki+22OjH3++TqaGeQ= ARC-Authentication-Results: i=1; imf20.hostedemail.com; dkim=pass header.d=suse.de header.s=susede2_rsa header.b=TStHlt6l; dkim=pass header.d=suse.de header.s=susede2_ed25519 header.b=jaU7pyWL; dkim=pass header.d=suse.de header.s=susede2_rsa header.b=TStHlt6l; dkim=pass header.d=suse.de header.s=susede2_ed25519 header.b=jaU7pyWL; spf=pass (imf20.hostedemail.com: domain of osalvador@suse.de designates 195.135.223.130 as permitted sender) smtp.mailfrom=osalvador@suse.de; dmarc=pass (policy=none) header.from=suse.de Received: from imap1.dmz-prg2.suse.org (imap1.dmz-prg2.suse.org [IPv6:2a07:de40:b281:104:10:150:64:97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 72AC822241; Mon, 13 May 2024 09:43:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1715593391; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=eCSaTwJWQtt3po9aVko9wqjZnxBfrkocdLOkhoLOyaY=; b=TStHlt6lc15M3c/WRCYx8XEoaK/ifWh1sjmebXIZfDGDLPq9FuJVCVlbAvj2uUQYQEYYXd EpbxKIoJUl6gbwWDk4lttBvq9ymWH/TT06IQSdvMDXmS/tTS+bIqGQKdqKoH16ZrIWWsZ9 T1h/KlZEDmqQOl5xoGwo2mtIrBZZos4= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1715593391; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=eCSaTwJWQtt3po9aVko9wqjZnxBfrkocdLOkhoLOyaY=; b=jaU7pyWLTKKwCxzExE91qZC+j5R/sJ6+2Z9l44Xc3czk96fbdkbapGJNC36XhNLiMP1OGU 8zwzh5FWep6Fr9CA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1715593391; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=eCSaTwJWQtt3po9aVko9wqjZnxBfrkocdLOkhoLOyaY=; b=TStHlt6lc15M3c/WRCYx8XEoaK/ifWh1sjmebXIZfDGDLPq9FuJVCVlbAvj2uUQYQEYYXd EpbxKIoJUl6gbwWDk4lttBvq9ymWH/TT06IQSdvMDXmS/tTS+bIqGQKdqKoH16ZrIWWsZ9 T1h/KlZEDmqQOl5xoGwo2mtIrBZZos4= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1715593391; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=eCSaTwJWQtt3po9aVko9wqjZnxBfrkocdLOkhoLOyaY=; b=jaU7pyWLTKKwCxzExE91qZC+j5R/sJ6+2Z9l44Xc3czk96fbdkbapGJNC36XhNLiMP1OGU 8zwzh5FWep6Fr9CA== Received: from imap1.dmz-prg2.suse.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by imap1.dmz-prg2.suse.org (Postfix) with ESMTPS id 3757D1372E; Mon, 13 May 2024 09:43:11 +0000 (UTC) Received: from dovecot-director2.suse.de ([2a07:de40:b281:106:10:150:64:167]) by imap1.dmz-prg2.suse.org with ESMTPSA id CT7PCq/gQWYhSAAAD6G6ig (envelope-from ); Mon, 13 May 2024 09:43:11 +0000 Date: Mon, 13 May 2024 11:43:09 +0200 From: Oscar Salvador To: Matthew Wilcox Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org Subject: Re: [LSF/MM/BFP TOPIC] Deprecate SPARSEMEM and have only SPARSEMEM_VMEMMAP Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Action: no action X-Rspamd-Server: rspam03 X-Rspamd-Queue-Id: 362951C0005 X-Rspam-User: X-Stat-Signature: 1wyt5o8fo3fgtg3gysbrt873ifuucxu7 X-HE-Tag: 1715593392-354289 X-HE-Meta: U2FsdGVkX1/LwRsWfWkGB3ZCD5EEgstOY3NerzWaJnrfWEsKIuA7YQazCNZnkeEcxO0GMAE/92echhNyAbD8f3/c/CEgG5zZ41NWDQuAxpPI8NRobXcf28rN9B+VF/eSIvoWYTVcM0gp3lak9WGoh1b4Icie1lVnqj38c7DNzJNl6+dCrcRsuaOoLyxyjFIBA6K+FBme/kfDZh6sILpr+/KFtmCHWD1cGz+1v+gPlNY6CWZnDIuj399aNr3Hvd6cYq0ANhygDTOKJjl2QiUerw9A3KeOKAxGUF5EdwHcf8gCL5Bo7b9sLnXXDPwTBLklpkKrl5dGsrJ4bcnPIJjd/ZTaorftOt2wHFWV6b1KEVqQqMjZrUgPNcbbWe4x8gMcd7AOhddCsrjxQcTD3X0vJFpmnfJxmqVSHXI7xBwtZg0HH49ggaDpa2kRqLoMycxvMYVhpM/FuxPO5WZ91tLW9bNMEeI2GD1QpjSv3Jlukm4Syg0epu1Y7t5zF0tFXTP8byOnxA5VUGj3jiWCk/4G76Z0XpA5QNGV1i+M/ISDQNoeBzSk7A1mtYOQc2YiWP0AKL6HocS2VNNS4ltMk9Z3ahGgmD9J5otGTt/CaNkaysVawn8kRi/luy24qEuHa9sxjpPsdOzIHiaC6RUpPxzgKv8v6UbywssQxQxpLqTErE1GwtqUGiRNXdP/KuCHF4C6nhzH3nLtdtomD0OpCUFljQ2PVzUlLgnQ32LqYqJbBXaa8ApJEmPEnkrNa52ISeh6pWhLVPcOd6KDHx6HS5TTMn8FfVo5R5CQCvCJ5MzQb+644niz6c6SwVEg0ghiwD1120wAPx/TrZD3MCL8tZfvOdY/k/Zm8C6jT8wjL31Ei5MCxSYhwQV2sAl2FXb094bp4ZAJxznj8xa/Zx7EMdanXrXuHhpHoOZtXQH6rd152g1rpD34NxJZdQC8Nt/sK8aiEWjBRGJAVQ8xXOcOMMP +97A5SKM YrJpBBP7mFd2GAK4etxI1FF0bXK+QuhhrihXkKmyLwreG1n6X++aza98SSBKgYkjfuKY/V6HLnHWmkGcSx/MXTmY/5jyIvzCKdkGDMwtjbumF/XQPED76CYw5ugDbjzgUS981AYzyDHNB5b+cJz9Vckzx25YH5Fnh1JkaUcPJApbWdSmPL5Yv6/NPdXoDoObnfwpDxjXmT0mZgANpcil7KHPcMyM/Dzh10vXz9u+EphtVBEpBfT8tbOchAw== X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: On Fri, May 10, 2024 at 11:03:58PM +0100, Matthew Wilcox wrote: > I'm a little concerned about having this conversation without the > affected architecture maintainers in the room. However, I can speak to > PA-RISC. Yes, having the architecture maintainers would be great. > Early models have a dense memory layout and we need not be concerned > with them. I'm not quite sure about the PA-7200 to PA-8500 ccio based > machines, would need to do some research. For the PA-8500+ astro based > machines, the 256MB that would be in the range 3.75GB to 4GB is > relocated to 67.75-68GB to leave space for PCI mmio. So if you have > a machine with 8GB of memory (fairly typical for a J6000 machine), > you'd have three ranges of memory: > > 0-3.75GB > 4-8GB > 67.75-68GB > > and I'd like to see an analysis of how laying out memmap would differ > for those machines. Maybe Mike can prove me wrong, but I assume that memblock will report the above ranges as memory, and the 3.75GB to 4GB as somewhat reserved. Then, we only mark those sections falling within the ranges reported as having memory by memblock as present, and we only populate the memmap for present sections. So, those ranges from above will be represented by present sections and hence with the vmemmap populated, and anything that falls off will not. I am not sure if I got your concern right though. > The PA-8800+ pluto chipset does something similar, except it > supports more memory and more PCI mmio, so a 32GB rp3440 would have > a memmap: > > 0-3GB > 4-32GB > 259-260GB > > I think this would actually work better as three zones rather than > three sections. It might match quite well with the TAO proposal. But those are not really sections, are they? But rather memory ranges. Checking the code from parisc, sections are at 128MB granularity. So you will have 0-3GB -> 0 .. 23 section (memmap populated) 4-32GB -> 31 .. 255 section (memmap populated) 259-260GB -> 2071 .. 2079 section (memmap populated) -- Oscar Salvador SUSE Labs