linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Alexander Krabler <Alexander.Krabler@kuka.com>
To: Frank van der Linden <fvdl@google.com>, Vlastimil Babka <vbabka@suse.cz>
Cc: Mike Galbraith <efault@gmx.de>,
	"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Dennis Schimmel <Dennis.Schimmel@kuka.com>,
	Daniel Braunwarth <Daniel.Braunwarth@kuka.com>,
	Hugh Dickins <hughd@google.com>
Subject: Re: Realtime threads delayed due to kcompactd0
Date: Tue, 5 Aug 2025 14:11:37 +0000	[thread overview]
Message-ID: <DU0PR01MB103853936E7A3476080F411BF8222A@DU0PR01MB10385.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <CAPTztWZpnX1j8-7yeppVUsxE=O9hbVeqricDjZt8_pnN7a-kBQ@mail.gmail.com>

On Fri, Aug 1, 2025 at 9:27 PM Frank van der Linden <fvdl@google.com> wrote:
> Another idea is to minimize the time that a migration PTE is in place
> for an mlocked page, Hugh (cc-ed) mentioned this in an offline
> discussion. E.g. skip any mlocked pages in the first pass, and just
> add them to a list. Then, do that list separately, but do them one by
> one. There is somewhat similar logic in migrate_pages_sync for pages
> that might need extra work / locking.

Another idea might be, that the blocked task migrates the page it is blocked on
by itself, removes the migration PTE and continues?
Doing the work itself instead of waiting for another thread to do the work.
Would that be possible?

This would solve the priority inversion problem and should be way more
deterministic than the current situation.

Alexander

KUKA Deutschland GmbH   Board of Directors: Michael Jürgens (Chairman), Dirk Busch, Johan Naten, Hui Zhang   Registered Office: Augsburg HRB 14914

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of contents of this e-mail is strictly forbidden.

Please consider the environment before printing this e-mail.

      reply	other threads:[~2025-08-05 14:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-25  5:30 Alexander Krabler
2025-07-31 18:34 ` Frank van der Linden
2025-07-31 18:41   ` Vlastimil Babka
2025-08-01  2:46     ` Mike Galbraith
2025-08-01  9:58       ` Vlastimil Babka
2025-08-01 11:23         ` Alexander Krabler
2025-08-01 12:57           ` Vlastimil Babka
2025-08-01 13:40             ` Alexander Krabler
2025-08-07 10:48               ` Vlastimil Babka
2025-08-07 12:21                 ` Hugh Dickins
2025-08-07 15:49                   ` Alexander Krabler
2025-08-08  7:37                     ` Vlastimil Babka
2025-08-20 14:29                       ` Sebastian Andrzej Siewior
2025-08-01 19:27         ` Frank van der Linden
2025-08-05 14:11           ` Alexander Krabler [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=DU0PR01MB103853936E7A3476080F411BF8222A@DU0PR01MB10385.eurprd01.prod.exchangelabs.com \
    --to=alexander.krabler@kuka.com \
    --cc=Daniel.Braunwarth@kuka.com \
    --cc=Dennis.Schimmel@kuka.com \
    --cc=efault@gmx.de \
    --cc=fvdl@google.com \
    --cc=hughd@google.com \
    --cc=linux-mm@kvack.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=vbabka@suse.cz \
    /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