From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: linux4.19/5.1/5.2: build with ELFv2 ABI on ppc64 big endian
Date: Sat, 13 Jul 2019 06:29:16 +0200 [thread overview]
Message-ID: <20190713042916.-mPc7tucL68a-vegl90wUAo_GTol6yPoCxs1qBkquXk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-13064@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 900 bytes --]
New comment by pullmoll on void-packages repository
https://github.com/void-linux/void-packages/pull/13064#issuecomment-511086121
Comment:
Oh yes, this seems to make a **big** difference from my impression. Tested `ppc64` with kernel `5.2.0`.
The system startup feels like it is twice as fast (or not slow) as before. Running an update with `xi -u` also went noticeably faster, also for the `dracut` + `grub` updates.
Edit: Actually the huge difference was because I removed `page_poison=1` from the `/etc/default/grub` command line for ppc64-glibc and only this time saw the effects. This is because I have two systems, glibc and musl, on one HDD and two times `/boot/grub` on the root partitions. So it takes two rounds of `update-grub`, on on each arch, to make any changes effective.
So on an unrelated note: If you want some more speed, disable page poisoning on the Linux command line.
next prev parent reply other threads:[~2019-07-13 4:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 17:48 [PR PATCH] " voidlinux-github
2019-07-13 3:01 ` voidlinux-github
2019-07-13 4:05 ` voidlinux-github
2019-07-13 4:29 ` voidlinux-github [this message]
2019-07-13 7:19 ` [PR PATCH] [Merged]: " voidlinux-github
2019-07-13 13:27 ` voidlinux-github
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=20190713042916.-mPc7tucL68a-vegl90wUAo_GTol6yPoCxs1qBkquXk@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).