From: Oscar Salvador <osalvador@suse.de>
To: Matthew Wilcox <willy@infradead.org>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org
Subject: Re: [LSF/MM/BFP TOPIC] Deprecate SPARSEMEM and have only SPARSEMEM_VMEMMAP
Date: Mon, 13 May 2024 12:12:44 +0200 [thread overview]
Message-ID: <ZkHnnL8PjqUmiCEC@localhost.localdomain> (raw)
In-Reply-To: <ZkHgrTo7Sp9AxpRp@localhost.localdomain>
On Mon, May 13, 2024 at 11:43:09AM +0200, Oscar Salvador wrote:
> 0-3GB -> 0 .. 23 section (memmap populated)
> 4-32GB -> 31 .. 255 section (memmap populated)
> 259-260GB -> 2071 .. 2079 section (memmap populated)
And just to add more info, considering a 128MB section granularity (which seems
to be what paric has) a PAGE_SIZE of 4KB (not really sure which page size parisc
can deal with), PAGES_PER_SECTION then being 32768 and the vmemmap range starting
at 0xffffea0000000000, we would have the following vmemmap layout:
0-3GB -> 0xffffea0000000000 - 0xffffea0003000000
4-32GB -> 0xffffea0004000000 - 0xffffea0007800000
259-260GB -> 0xffffea0023e00000 - 0xffffea0024e00000
I am not sure though whether we can hit any limitation when it comes to
the vmemmap space we have available.
--
Oscar Salvador
SUSE Labs
next prev parent reply other threads:[~2024-05-13 10:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 9:03 [LSF/MM/BFP TOPIC] Deprecate SPARSEMEM and have only SPARSEMEM_VMEMMAP Oscar Salvador
2024-05-10 22:03 ` Matthew Wilcox
2024-05-13 9:43 ` Oscar Salvador
2024-05-13 10:12 ` Oscar Salvador [this message]
2024-05-13 23:02 ` Mike Rapoport
2024-05-12 13:45 ` Mike Rapoport
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZkHnnL8PjqUmiCEC@localhost.localdomain \
--to=osalvador@suse.de \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=willy@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).