mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sergey Organov <sorganov@gmail.com>
To: Jon Masters <jcm@jonmasters.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Selecting MMU page size for an architecture
Date: Mon, 24 Jan 2022 16:41:26 +0300	[thread overview]
Message-ID: <871r0x45fd.fsf@osv.gnss.ru> (raw)
In-Reply-To: <CACCGGCfQp7W3dCPNDh9sWTBCpC-adFwhhDaoHhwx8dyXa3UBeA@mail.gmail.com> (Jon Masters's message of "Sun, 23 Jan 2022 21:05:24 -0500")

Hi Jon,

Jon Masters <jcm@jonmasters.org> writes:

> Hey Sergey,
>
> On Thu, Dec 23, 2021 at 8:15 AM Sergey Organov <sorganov@gmail.com> wrote:
>
>> 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?
>
> If you want maximum compatibility with existing source written for
> industry at large (e.g. x86/Arm) and even the assumptions in other
> devices (and their firmware) you might connect (PCI, or even on-SoC)
> then you'll want to go with 4K. However, if I were designing a brand
> new architecture today and didn't care about legacy, I would
> definitely consider following Apple into 16K.

I don't think we will have issues with device drivers because of this,
but even if so, I believe we'll be able to fix that, so I get your
advice as +1 in favor of 16K pages.

Thanks for sharing!

-- Sergey Organov

      reply	other threads:[~2022-01-24 13:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-22 22:34 Sergey Organov
2022-01-24  2:05 ` Jon Masters
2022-01-24 13:41   ` Sergey Organov [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=871r0x45fd.fsf@osv.gnss.ru \
    --to=sorganov@gmail.com \
    --cc=jcm@jonmasters.org \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®