[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240902145252.1d2590dbed417d223b896a00@linux-foundation.org>
Date: Mon, 2 Sep 2024 14:52:52 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Kent Overstreet <kent.overstreet@...ux.dev>
Cc: Michal Hocko <mhocko@...nel.org>, Christoph Hellwig <hch@....de>, Yafang
Shao <laoar.shao@...il.com>, jack@...e.cz, Vlastimil Babka
<vbabka@...e.cz>, Dave Chinner <dchinner@...hat.com>, Christian Brauner
<brauner@...nel.org>, Alexander Viro <viro@...iv.linux.org.uk>, Paul Moore
<paul@...l-moore.com>, James Morris <jmorris@...ei.org>, "Serge E. Hallyn"
<serge@...lyn.com>, linux-fsdevel@...r.kernel.org, linux-mm@...ck.org,
linux-bcachefs@...r.kernel.org, linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2 v2] remove PF_MEMALLOC_NORECLAIM
On Mon, 2 Sep 2024 05:53:59 -0400 Kent Overstreet <kent.overstreet@...ux.dev> wrote:
> On Mon, Sep 02, 2024 at 11:51:48AM GMT, Michal Hocko wrote:
> > The previous version has been posted in [1]. Based on the review feedback
> > I have sent v2 of patches in the same threat but it seems that the
> > review has mostly settled on these patches. There is still an open
> > discussion on whether having a NORECLAIM allocator semantic (compare to
> > atomic) is worthwhile or how to deal with broken GFP_NOFAIL users but
> > those are not really relevant to this particular patchset as it 1)
> > doesn't aim to implement either of the two and 2) it aims at spreading
> > PF_MEMALLOC_NORECLAIM use while it doesn't have a properly defined
> > semantic now that it is not widely used and much harder to fix.
> >
> > I have collected Reviewed-bys and reposting here. These patches are
> > touching bcachefs, VFS and core MM so I am not sure which tree to merge
> > this through but I guess going through Andrew makes the most sense.
> >
> > Changes since v1;
> > - compile fixes
> > - rather than dropping PF_MEMALLOC_NORECLAIM alone reverted eab0af905bfc
> > ("mm: introduce PF_MEMALLOC_NORECLAIM, PF_MEMALLOC_NOWARN") suggested
> > by Matthew.
>
> To reiterate:
>
It would be helpful to summarize your concerns.
What runtime impact do you expect this change will have upon bcachefs?
Powered by blists - more mailing lists