From: "Theodore Tso" <tytso@mit.edu>
To: Mario Lohajner <mario_lohajner@rocketmail.com>
Cc: Baokun Li <libaokun1@huawei.com>,
adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, Yang Erkun <yangerkun@huawei.com>,
libaokun9@gmail.com
Subject: Re: [PATCH] ext4: add optional rotating block allocation policy
Date: Sun, 8 Feb 2026 14:58:49 -0500 [thread overview]
Message-ID: <20260208195849.GA74984@macsyma.lan> (raw)
In-Reply-To: <9e520492-9b26-487f-9d60-7e0625c987c9@rocketmail.com>
On Sun, Feb 08, 2026 at 12:47:12PM +0100, Mario Lohajner wrote:
>
> Someone comes forward with a fork, saying:
> “Here is 'my fork'. I believe it may work well for 'some dishes'.”
Give me *proof* that it works on 'some dishes' in terms of actual
perfomance, specifiying real-world workloads, and real-world devices,
and we can talk. "I believe" is not enough for code that upstream has
to test and maintain indefinitely. If it works for you, it's open
source. You can run with an out-of-tree on your systems. But if you
want us to accept it upstream, you need to provide something more than
"I believe".
Cheers,
- Ted
next prev parent reply other threads:[~2026-02-08 19:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260204033112.406079-1-mario_lohajner.ref@rocketmail.com>
2026-02-04 3:31 ` [PATCH] ext4: add optional rotating block allocation policy Mario Lohajner
2026-02-04 3:53 ` Andreas Dilger
2026-02-04 11:07 ` Mario Lohajner
2026-02-04 21:37 ` Theodore Tso
2026-02-04 6:29 ` Baokun Li
2026-02-04 11:06 ` Mario Lohajner
2026-02-05 3:52 ` Baokun Li
2026-02-05 12:23 ` Mario Lohajner
2026-02-06 1:42 ` Theodore Tso
2026-02-06 19:25 ` Mario Lohajner
2026-02-07 5:31 ` Theodore Tso
2026-02-07 12:45 ` Mario Lohajner
2026-02-07 17:55 ` Theodore Tso
2026-02-08 4:11 ` Mario Lohajner
2026-02-08 11:47 ` Mario Lohajner
2026-02-08 19:58 ` Theodore Tso [this message]
2026-02-22 23:08 ` Mario Lohajner
2026-02-06 23:53 ` Andreas Dilger
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=20260208195849.GA74984@macsyma.lan \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=libaokun1@huawei.com \
--cc=libaokun9@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mario_lohajner@rocketmail.com \
--cc=yangerkun@huawei.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