[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231102023615.jsv2ffe4rbivgsja@moria.home.lan>
Date: Wed, 1 Nov 2023 22:36:15 -0400
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: Christian Brauner <brauner@...nel.org>
Cc: Mateusz Guzik <mjguzik@...il.com>,
Dave Chinner <david@...morbit.com>,
Dave Chinner <dchinner@...hat.com>,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-bcachefs@...r.kernel.org,
Alexander Viro <viro@...iv.linux.org.uk>
Subject: Re: (subset) [PATCH 22/32] vfs: inode cache conversion to hash-bl
On Tue, Oct 31, 2023 at 12:02:47PM +0100, Christian Brauner wrote:
> > The follow up including a statement about "being arsed" once more was
> > to Christian, not you and was rather "tongue in cheek".
>
> Fyi, I can't be arsed to be talked to like that.
>
> > Whether the patch is ready for reviews and whatnot is your call to
> > make as the author.
>
> This is basically why that patch never staid in -next. Dave said this
> patch is meaningless without his other patchs and I had no reason to
> doubt that claim nor currently the cycles to benchmark and disprove it.
It was a big benefit to bcachefs performance, and I've had it in my tree
for quite some time. Was there any other holdup?
Powered by blists - more mailing lists