[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231220003709.vayf4rcip7c3hjk7@moria.home.lan>
Date: Tue, 19 Dec 2023 19:37:09 -0500
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: Matthew Wilcox <willy@...radead.org>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
linux-fsdevel@...r.kernel.org, tglx@...utronix.de, x86@...nel.org,
tj@...nel.org, peterz@...radead.org, mathieu.desnoyers@...icios.com,
paulmck@...nel.org, keescook@...omium.org,
dave.hansen@...ux.intel.com, mingo@...hat.com, will@...nel.org,
longman@...hat.com, boqun.feng@...il.com, brauner@...nel.org
Subject: Re: [PATCH 15/50] kernel/numa.c: Move logging out of numa.h
On Tue, Dec 19, 2023 at 10:52:33PM +0000, Matthew Wilcox wrote:
> On Fri, Dec 15, 2023 at 10:26:14PM -0500, Kent Overstreet wrote:
> > diff --git a/kernel/numa.c b/kernel/numa.c
> > new file mode 100644
> > index 000000000000..c24c72f45989
> > --- /dev/null
> > +++ b/kernel/numa.c
>
> Should this be a new file or would these functions fit better in, eg,
> mempolicy.c which is already built only if CONFIG_NUMA?
that does look like a bit of a disorganized dumping ground though, I
wonder if anyone would want to start mm/numa/ and do a bit of
organizing?
Powered by blists - more mailing lists