All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brandon Ho <brandonho667@gmail.com>
To: rpm@xenomai.org
Cc: brandonho667@gmail.com, brho@relativityspace.com,
	jsridharan@relativityspace.com, xenomai@lists.linux.dev
Subject: Re: Minor page faults from memory compaction causing in-band transitions
Date: Mon, 13 Apr 2026 11:19:29 -0700	[thread overview]
Message-ID: <20260413181929.1801013-1-brho@relativityspace.com> (raw)
In-Reply-To: <87v7e8yzhj.fsf@xenomai.org>

Thank you for the responses! I recently came across the
`compact_unevictable_allowed` sysctl option and it seems like it could be a
good fit for our use case. Setting it to 0 would prevent the kernel from
compacting/migrating locked pages, which should eliminate the minor faults
we're seeing during compaction.

Could we possibly set `compact_unevictable_allowed=0` by default when
CONFIG_EVL is enabled?

https://www.infradead.org/~mchehab/kernel_docs/admin-guide/sysctl/vm.html#compact-unevictable-allowed

  reply	other threads:[~2026-04-13 18:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 23:14 Minor page faults from memory compaction causing in-band transitions Brandon Ho
2026-04-02 21:23 ` Jan Kiszka
2026-04-03 12:55 ` Philippe Gerum
2026-04-13 18:19   ` Brandon Ho [this message]
2026-04-13 18:31     ` Philippe Gerum
     [not found]       ` <CY1P110MB0760484C0708C37BA89D5A02D624A@CY1P110MB0760.NAMP110.PROD.OUTLOOK.COM>
2026-04-14  7:05         ` Philippe Gerum
2026-04-14  7:37       ` Florian Bezdeka
2026-04-14  7:42         ` Philippe Gerum
2026-04-14  7:52           ` Philippe Gerum
  -- strict thread matches above, loose matches on Subject: below --
2026-05-04 17:52 Jay Sridharan
2026-05-06  7:40 ` Philippe Gerum
2026-04-13 19:45 Jay Sridharan
2026-03-31 22:52 Brandon Ho

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=20260413181929.1801013-1-brho@relativityspace.com \
    --to=brandonho667@gmail.com \
    --cc=brho@relativityspace.com \
    --cc=jsridharan@relativityspace.com \
    --cc=rpm@xenomai.org \
    --cc=xenomai@lists.linux.dev \
    /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.