Github messages for voidlinux
 help / color / mirror / Atom feed
From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: linux4.19, linux5.1, linux5.2: use 4kB pages in ppc64/ppc64le kernels
Date: Sun, 14 Jul 2019 12:53:04 +0200	[thread overview]
Message-ID: <20190714105304.4SggPg30JuplaQEVjiAUd3PTuvp--K5rZgi765s_2T8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13088@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1310 bytes --]

There's a merged pull request on the void-packages repository

linux4.19, linux5.1, linux5.2: use 4kB pages in ppc64/ppc64le kernels
https://github.com/void-linux/void-packages/pull/13088
Description: Previously the kernels were using 64kB pages. This is only supported in hardware from POWER8 onwards (so older platforms needed to emulate it) and was done mostly because of compatibility with other ppc64le distros, which typically default to 64k (because of targeting servers). However, turns out most of these compatibility issues were a non-concern (64kB VM guests work fine on 4kB hosts, qt5-webengine still works despite hardcoding 64kB (probably just uses a bit of extra memory),  my ext4 filesystems still mount, and I haven't noticed any other troubles.

Using 4kB pages is much better suited for desktops (the only workloads benefiting from 64kB are exclusively server ones, there isn't a lot of them, and the difference is minimal; these servers also usually have lots of RAM) and is generally the saner and more compatible with the rest of the world option. Drivers also like them better (like Nouveau on newer graphics cards), it makes using guard pages possible, wastes less system memory, etc.

People who wish to use 64kB pages can compile their own kernel, no point in shipping a variant.

      parent reply	other threads:[~2019-07-14 10:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-13 14:11 [PR PATCH] " voidlinux-github
2019-07-13 14:11 ` voidlinux-github
2019-07-14 10:53 ` voidlinux-github [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=20190714105304.4SggPg30JuplaQEVjiAUd3PTuvp--K5rZgi765s_2T8@z \
    --to=voidlinux-github@inbox.vuxu.org \
    --cc=ml@inbox.vuxu.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).