linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: kirill@shutemov.name, Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@redhat.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>,
	Kiryl Shutsemau <kas@kernel.org>
Subject: Re: [PATCH] tools/mm: Add madvise tool
Date: Fri, 5 Sep 2025 12:56:24 +0200	[thread overview]
Message-ID: <aLrB2D-DjK8pFLHa@tiehlicka> (raw)
In-Reply-To: <0b22e23d-f00b-47da-8e62-c8b0ced05e4e@lucifer.local>

On Fri 05-09-25 11:16:38, Lorenzo Stoakes wrote:
> On Fri, Sep 05, 2025 at 11:17:10AM +0200, Michal Hocko wrote:
> >
> > 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.
> 
> To give my own 2 pence on this :>)
> 
> I think this is actually quite useful because it invokes process_madvise() and
> so can be used for experiments against other processes in a way that'd you'd
> have to write code for otherwise.

I am not questioning usefulness of the tool itself.

> I think it's useful to keep in sync with kernel as if we add more remote process
> madvise functionality this can be updated with it.

I just do not see any value in having it in the tree. It doesn't use (or
rely on) any kernel infrastructure and it can happily live outside of
the tree. New madvise functionality requires a runtime support rather
than a support in the current source tree.

We are certainly not pulling in other potentially useful tools
into the kernel tree in for some it was even really hard/impossible to
be merged yet they would benefit from a close lockstep with kernel
sources.


-- 
Michal Hocko
SUSE Labs


  reply	other threads:[~2025-09-05 10:56 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 [this message]
2025-09-05 11:02       ` Lorenzo Stoakes
2025-09-05 10:21   ` Kiryl Shutsemau
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=aLrB2D-DjK8pFLHa@tiehlicka \
    --to=mhocko@suse.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@redhat.com \
    --cc=kas@kernel.org \
    --cc=kirill@shutemov.name \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.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