From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E34BDEB64DC for ; Thu, 6 Jul 2023 19:32:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232059AbjGFTcC (ORCPT ); Thu, 6 Jul 2023 15:32:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45912 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231465AbjGFTcA (ORCPT ); Thu, 6 Jul 2023 15:32:00 -0400 Received: from out-27.mta0.migadu.com (out-27.mta0.migadu.com [IPv6:2001:41d0:1004:224b::1b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B7E8D1BD3 for ; Thu, 6 Jul 2023 12:31:55 -0700 (PDT) Date: Thu, 6 Jul 2023 15:31:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1688671913; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=PGCCHwwA0cqXeEKD4KLulUCgMqGwkQRRxiEeo6W/m4I=; b=uLSIk5UJnWZnWg1Sh4p4US2Xr0/a9bs9JhQ9SV/5kZaoyMtIMdu/mExFa/MPGbqDQack9r 2/zSEQha87UaghKVQv2E9fW4Mzs9erE734Q2T8cjrYVRcWjpQmj6/HUq8rGWDH8EQ5dMzc ULREbxOP4mTmET86ulXYaWEv7X9uxwo= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Kent Overstreet To: Eric Sandeen Cc: Josef Bacik , torvalds@linux-foundation.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-bcachefs@vger.kernel.org, djwong@kernel.org, dchinner@redhat.com, sandeen@redhat.com, willy@infradead.org, tytso@mit.edu, bfoster@redhat.com, jack@suse.cz, andreas.gruenbacher@gmail.com, brauner@kernel.org, peterz@infradead.org, akpm@linux-foundation.org, dhowells@redhat.com Subject: Re: [GIT PULL] bcachefs Message-ID: <20230706193146.f2ktfnsxhrfokasp@moria.home.lan> References: <20230626214656.hcp4puionmtoloat@moria.home.lan> <20230706155602.mnhsylo3pnief2of@moria.home.lan> <20230706164055.GA2306489@perftesting> <20230706173819.36c67pf42ba4gmv4@moria.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Migadu-Flow: FLOW_OUT Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 06, 2023 at 02:17:29PM -0500, Eric Sandeen wrote: > On 7/6/23 12:38 PM, Kent Overstreet wrote: > > Right now what I'm hearing, in particular from Redhat, is that they want > > it upstream in order to commit more resources. Which, I know, is not > > what kernel people want to hear, but it's the chicken-and-the-egg > > situation I'm in. > > I need to temper that a little. Folks in and around filesystems and storage > at Red Hat find bcachefs to be quite compelling and interesting, and we've > spent some resources in the past several months to investigate, test, > benchmark, and even do some bugfixing. > > Upstream acceptance is going to be a necessary condition for almost any > distro to consider shipping or investing significantly in bcachefs. But it's > not a given that once it's upstream we'll immediately commit more resources > - I just wanted to clarify that. Yeah, I should probably have worder that a bit better. But in the conversations I've had with people at other companies it does sound like the interest is there, it's just that filesystem/storage teams are not so big these days as to support investing in something that is not yet mainlined. > It is a tough chicken and egg problem to be sure. That said, I think you're > right Kent - landing it upstream will quite likely encourage more interest, > users, and hopefully developers. Gotta start somewhere :) > Maybe it'd be reasonable to mark bcachefs as EXPERIMENTAL or similar in > Kconfig, documentation, and printks - it'd give us options in case it > doesn't attract developers and Kent does get hit by a bus or decide to go > start a goat farm instead (i.e. in the worst case, it could be yanked, > having set expectations.) Yeah, it does need to be marked EXPERIMENTAL initially, regardless - staged rollout please, not everyone all at once :)