linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kiryl Shutsemau <kirill@shutemov.name>
To: Michal Hocko <mhocko@suse.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	 David Hildenbrand <david@redhat.com>,
	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	 "Liam R . Howlett" <Liam.Howlett@oracle.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	 Mike Rapoport <rppt@kernel.org>,
	Suren Baghdasaryan <surenb@google.com>,
	linux-mm@kvack.org,  Usama Arif <usamaarif642@gmail.com>
Subject: Re: [PATCH] tools/mm: Add madvise tool
Date: Fri, 5 Sep 2025 11:21:30 +0100	[thread overview]
Message-ID: <v3rbjkvckce5jck5mugtqmevtrpckr7mqxzkdel4uawuvibikr@zeqfnti5p6zf> (raw)
In-Reply-To: <aLqqlkTpEM1SkvaE@tiehlicka>

On Fri, Sep 05, 2025 at 11:17:10AM +0200, Michal Hocko wrote:
> On Thu 04-09-25 18:57:29, Kirill A. Shutemov wrote:
> > From: Kiryl Shutsemau <kas@kernel.org>
> > 
> > Add a simple tool that allows to issue an advice on a process or a file.
> > 
> > It can be useful to experiment with effects of an advice on a workload
> > without modifying the workload itself.
> 
> Is there any reason to have this in the tree? This seems like a very
> trivial tools that doesn't really need to be in a lockstep with the
> kernel source.

There's no strong reason to move it in lockstep with kernel code. At
least for now.

The tool is useful to experiment with both kernel and workload behaviour
on an advice. Like, I see some oddities with MADV_COLLAPSE that makes it
give up easily where it shouldn't (will investigate later). I wouldn't
see them otherwise.

But you don't see it fitting kernel tree, I would not push back much.
I found the tool useful and decided to share.

> Also would it make more sense to send the pidfd fd to the tool directly
> so that it can benefit from a racefree pid->fd translation?

Hm. Do we have an easy way to open pidfd from shell?

I am not sure we care that much about the race for this tool.

-- 
  Kiryl Shutsemau / Kirill A. Shutemov


  parent reply	other threads:[~2025-09-05 10:21 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-04 17:57 kirill
2025-09-04 19:07 ` Liam R. Howlett
2025-09-05  3:26 ` wang lian
2025-09-05 10:28   ` Kiryl Shutsemau
2025-09-08  1:09     ` wang lian
2025-09-05  9:17 ` Michal Hocko
2025-09-05 10:16   ` Lorenzo Stoakes
2025-09-05 10:56     ` Michal Hocko
2025-09-05 11:02       ` Lorenzo Stoakes
2025-09-05 10:21   ` Kiryl Shutsemau [this message]
2025-09-05 11:02     ` Michal Hocko
2025-09-05 10:19 ` David Hildenbrand
2025-09-05 10:24   ` Kiryl Shutsemau
2025-09-05 10:33     ` David Hildenbrand
2025-09-05 10:35       ` Kiryl Shutsemau
2025-09-05 10:37 ` Lorenzo Stoakes
2025-09-05 13:35   ` Kiryl Shutsemau
2025-09-05 16:30   ` Kiryl Shutsemau
2025-09-05 10:45 ` Usama Arif
2025-09-05 10:59 ` Mike Rapoport
2025-09-05 13:36   ` Kiryl Shutsemau
2025-09-06  8:00     ` Mike Rapoport
2025-09-08 10:04       ` Kiryl Shutsemau
2025-09-10 11:34 ` [ANNOUNCE] mm-tools: Random tools MM-related tools Kiryl Shutsemau

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=v3rbjkvckce5jck5mugtqmevtrpckr7mqxzkdel4uawuvibikr@zeqfnti5p6zf \
    --to=kirill@shutemov.name \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mhocko@suse.com \
    --cc=rppt@kernel.org \
    --cc=surenb@google.com \
    --cc=usamaarif642@gmail.com \
    --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