public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: "Day, Timothy" <timday@amazon.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	"lsf-pc@lists.linux-foundation.org"
	<lsf-pc@lists.linux-foundation.org>,
	"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"jsimmons@infradead.org" <jsimmons@infradead.org>,
	Andreas Dilger <adilger@ddn.com>, "neilb@suse.de" <neilb@suse.de>
Subject: Re: [LSF/MM/BPF TOPIC] Lustre filesystem upstreaming
Date: Thu, 30 Jan 2025 06:28:20 -0800	[thread overview]
Message-ID: <20250130142820.GA401886@mit.edu> (raw)
In-Reply-To: <DD162239-D4B3-433C-A7C1-2DBEBFA881EC@amazon.com>

On Tue, Jan 28, 2025 at 04:35:46PM +0000, Day, Timothy wrote:
> My biggest question for LSF is around development model:
> Our current development model is still orthogonal to what
> most other subsystems/drivers do. But as we evolve, how do
> we demonstrate that our development model is reasonable?
> Sending the initial patches is one thing. Convincing everyone
> that the model is sustainable is another.

I suspect one of the reasons why most development is happening out-of-tree
is pretty much all of the users of Lustre are using distro (and very
often, Enterprise) kernels.  Are there any people outside of the core
Lustre team (most of whom are probably working for DDN?) that use
Lustre or can even test Lustre using the upstream kernel?

I'll let Andreas to comment further, but from my perspective, if we
want to upstreaming Lustre to be successful, perhaps one strategy
would be to make it easier for upstream users and developers to use
Lustre, perhaps in a smaller scale than what a typical DDN customer
would typically use.

Cheers,

					- Ted

  reply	other threads:[~2025-01-30 14:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-24 20:50 [LSF/MM/BPF TOPIC] Lustre filesystem upstreaming Day, Timothy
2025-01-24 21:09 ` Matthew Wilcox
2025-01-24 22:56   ` NeilBrown
2025-01-25  6:33   ` Day, Timothy
2025-01-28  6:14 ` Christoph Hellwig
2025-01-28 16:35   ` Day, Timothy
2025-01-30 14:28     ` Theodore Ts'o [this message]
2025-01-30 16:18       ` Day, Timothy
2025-01-30 16:56         ` Theodore Ts'o
2025-01-30 17:32           ` Day, Timothy
     [not found]       ` <4044F3FF-D0CE-4823-B104-0544A986DF7B@ddn.com>
2025-01-31 22:11         ` [Lsf-pc] " Amir Goldstein
2025-01-31 23:01           ` Day, Timothy
2025-02-01 10:55             ` Amir Goldstein
2025-02-01 13:59               ` Zorro Lang
2025-02-02 15:26                 ` Theodore Ts'o
2025-02-03  6:44                   ` Christoph Hellwig
2025-02-03 16:06                     ` Day, Timothy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250130142820.GA401886@mit.edu \
    --to=tytso@mit.edu \
    --cc=adilger@ddn.com \
    --cc=hch@infradead.org \
    --cc=jsimmons@infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=neilb@suse.de \
    --cc=timday@amazon.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox