linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Sergey Organov <sorganov@gmail.com>
To: linux-mm@kvack.org
Subject: Selecting MMU page size for a new architecture
Date: Fri, 24 Dec 2021 02:03:11 +0300	[thread overview]
Message-ID: <87o856yle8.fsf@osv.gnss.ru> (raw)

Hello,

We are building custom CPU and have an option to choose either 4K or 16K
MMU minimum page size that will then be fixed in the hardware. For
reasons unrelated to the Linux kernel we'd prefer 16K, but I have some
doubts.

What pros and cons for kernel and user-space operation 16K pages will
have over more usual 4K pages? Anything we should worry about?

Thanks,
-- Sergey Organov


                 reply	other threads:[~2021-12-23 23:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87o856yle8.fsf@osv.gnss.ru \
    --to=sorganov@gmail.com \
    --cc=linux-mm@kvack.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