Received-SPF: pass (google.com: domain of linux-numa-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Sat, 15 Jan 2022 08:09:48 -0800
From:   Andi Kleen <andi@firstfloor.org>
To:     Andreas Grapentin <andreas@grapentin.org>
Cc:     linux-numa@vger.kernel.org
Subject: Re: utility for numa placement of POSIX shared memory segments
Message-ID: <20220115160946.uwur26u3zyzcwvzo@two.firstfloor.org>
References: <D6DA3DAD-286C-4D15-A394-447546711B79@grapentin.org>
 <20220115100542.qanbvb6dhz27sdyj@parabolabook-BM15.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20220115100542.qanbvb6dhz27sdyj@parabolabook-BM15.localdomain>
User-Agent: NeoMutt/20170113 (1.7.2)
Precedence: bulk

On Sat, Jan 15, 2022 at 11:05:42AM +0100, Andreas Grapentin wrote:
> On Tue, Jan 11, 2022 at 07:28:37AM +0100, Andreas Grapentin wrote:
> > Hello,
> > 
> > I recently wrote out of necessity a small utility to move memory pages
> > of a posix named shared memory segment between NUMA nodes. A friend
> > pointed out that this utility could make a good addition to numactl,
> > maybe as a separate executable alongside migratepages.
> > 
> > The repository of the tools in question is already public and
> > available on github:
> > https://github.com/oaken-source/move_shmem_pages
> > 
> > Would this be a welcome addition to numactl? If so, I could prepare a
> > PR or two to the numactl github repository to add this functionality.

Thanks for the offer.

It could be useful, but numactl itself already has file shared memory
policy support, just not support for moving (and migrate_pages only
supports pid). So if it was added I would prefer having it as a new
argument to numactl instead of proliferating commands with different
syntax. It should be fairly straight forward there because
all the infrastructure to parse the arguments and map the pages is
already there.

-Andi