linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Gabriele Monaco <gmonaco@redhat.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Subject: Re: [PATCH] sched: Move task_mm_cid_work to mm delayed work
Date: Mon, 09 Dec 2024 09:04:40 +0100	[thread overview]
Message-ID: <d195fe29c43d793a4811beac57e205d1f324c8c5.camel@redhat.com> (raw)
In-Reply-To: <445b4203-940d-4817-bd45-9da757f22450@efficios.com>


On Fri, 2024-12-06 at 09:06 -0500, Mathieu Desnoyers wrote:
> 
> Thinking back on this, you'll want a program that does the following
> on a system with N CPUs:
> 
> - Phase 1: run one thread per cpu, pinned on each cpu. Print the
>    mm_cid from each thread with the cpu number every second or so.
> 
> - Exit all threads except the main thread, join them from the main
>    thread,
> 
> - Phase 2: the program is now single-threaded. We'd expect the
>    mm_cid value to converge towards 0 as the periodic task clears
>    unused CIDs.
> 
> So I think in phase 2 we can have an actual automated test: If after
> an order of magnitude more time than the 100ms delay between periodic
> tasks we still observe mm_cid > 0 in phase 2, then something is
> wrong.
> 
> Thoughts ?

Nice idea, that looks neat and fairly simple. Also by printing every
second we would get the threads running in short bursts and, probably,
the test would fail with the current implementation, depending how long
we wait, of course.
I can try to draft something to test my implementation.

Thanks,
Gabriele



  reply	other threads:[~2024-12-09  8:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05  8:31 Gabriele Monaco
2024-12-05 14:33 ` Gabriele Monaco
2024-12-05 16:25   ` Mathieu Desnoyers
2024-12-06  8:53     ` Gabriele Monaco
2024-12-06 14:06       ` Mathieu Desnoyers
2024-12-09  8:04         ` Gabriele Monaco [this message]
2024-12-09 13:45         ` Gabriele Monaco
2024-12-09 15:33           ` Mathieu Desnoyers
2024-12-09 15:48             ` Mathieu Desnoyers
2024-12-11 12:27               ` Gabriele Monaco
2024-12-11 17:07                 ` Mathieu Desnoyers
2024-12-12 11:09                   ` Gabriele Monaco
2024-12-12 14:06                     ` Mathieu Desnoyers

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=d195fe29c43d793a4811beac57e205d1f324c8c5.camel@redhat.com \
    --to=gmonaco@redhat.com \
    --cc=mathieu.desnoyers@efficios.com \
    /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