All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Gerum <rpm@xenomai.org>
To: Jay Sridharan <jayasurya.sridharan@gmail.com>
Cc: Brandon Ho <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: Wed, 06 May 2026 09:40:52 +0200	[thread overview]
Message-ID: <87ecjpj88r.fsf@xenomai.org> (raw)
In-Reply-To: <CAGNKwhBekLJqcrNi3u+ZMKrpqU-6X7_1DXJ7Grpz=R8FkYrjfg@mail.gmail.com> (Jay Sridharan's message of "Mon, 4 May 2026 10:52:04 -0700")


Hi Jay,

Looks good to me, very useful for understanding some of the intricacies
of virtual memory management vs real-time workloads, and how to address
them. I would happily merge a commit with this information as-is.

[I noticed a couple of hiccups breaking the patch format likely due to
the MUA].

Jay Sridharan <jayasurya.sridharan@gmail.com> writes:

> Hi Phillipe,
>
> Let me know what you think of this patch for the docs:
>
> diff --git a/content/core/caveat.md b/content/core/caveat.md
> index b24e270..e11d605 100644
> --- a/content/core/caveat.md
> +++ b/content/core/caveat.md
> @@ -70,6 +70,68 @@ which depend on instrumenting the spinlock constructs (e.g.
>  `CONFIG_DEBUG_PREEMPT`), you may want to disable all the related kernel
>  options, starting with `CONFIG_SMP`.
>
> +### Memory compaction and page migration impact real-time behavior
> {#caveat-memory-compaction}

<line wrapped>

> +
> +- Launch EVL threads. At the end of initialization, but before
> calling mlockall..

<line wrapped>

-- 
Philippe.

  reply	other threads:[~2026-05-06  7:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-04 17:52 Minor page faults from memory compaction causing in-band transitions Jay Sridharan
2026-05-06  7:40 ` Philippe Gerum [this message]
2026-05-14 19:02   ` [PATCH] update caveat.md about memory compaction Jay Sridharan
2026-05-14 19:28     ` Philippe Gerum
  -- strict thread matches above, loose matches on Subject: below --
2026-04-13 19:45 Minor page faults from memory compaction causing in-band transitions Jay Sridharan
2026-03-31 23:14 Brandon Ho
2026-04-02 21:23 ` Jan Kiszka
2026-04-03 12:55 ` Philippe Gerum
2026-04-13 18:19   ` Brandon Ho
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
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=87ecjpj88r.fsf@xenomai.org \
    --to=rpm@xenomai.org \
    --cc=brandonho667@gmail.com \
    --cc=brho@relativityspace.com \
    --cc=jayasurya.sridharan@gmail.com \
    --cc=jsridharan@relativityspace.com \
    --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.