All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Oscar Salvador <osalvador@suse.de>
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: Sun, 12 May 2024 07:45:15 -0600	[thread overview]
Message-ID: <ZkDH6w0wv0pzr9rI@kernel.org> (raw)
In-Reply-To: <Zj3i0pCJd3ETxQNU@localhost.localdomain>

On Fri, May 10, 2024 at 11:03:14AM +0200, Oscar Salvador wrote:
> Hi all,
> 
> I would like to discuss the following topic in the LSFMM.
> 
> We have SPARSEMEM memory model and SPARSEMEM_VMEMMAP, where the only difference
> between the two of them is that the latter allocates a virtual chunk to represent
> the memmap array, which speeds operations like
> page_to_pfn/pfn_to_page/nth_page/folio_page_idx.
 
...
 
> I did some research on which arches use CONFIG_SPARSE_MEMMAP/VMEMMAP or
> none(using flatmem?).

FLATMEM it is.
                    
>  SPARSE_MEMMAP       SPARSE_VMEMMAP
>  arc
>  arm              X
>  arm64            X                     X
>  csky
>  hexagon 
>  loongarch        X                     X
>  m68k
>  microblaze
>  mips             X
>  nios2
>  openrisc
>  parisc
>  powerpc          X                     X
>  riscv            X                     X
>  s390             X                     X
>  sh               X
>  sparc            X                     X
>  um
>  x86              X                     X
>  xtensa
> 
> arm, mips, parisc and sh operate with SPARSE_MEMMAP but are lacking code for
> SPARSE_VMEMMAP.

arm can use "sparse flatmem" in the sense that it can free unused parts of
the memory map so FLATMEM does not have memory overhead with sparsely
located memory banks. So possible we can just drop SPARSEMEM on arm.

But I agree with Matthew that for this discussion we'd need arch
maintainers to participate.

> Thanks
> 
> -- 
> Oscar Salvador
> SUSE Labs
> 

-- 
Sincerely yours,
Mike.


      parent reply	other threads:[~2024-05-12 13:47 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
2024-05-13 23:02     ` Mike Rapoport
2024-05-12 13:45 ` Mike Rapoport [this message]

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=ZkDH6w0wv0pzr9rI@kernel.org \
    --to=rppt@kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=osalvador@suse.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.