mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mario Lohajner <mario_lohajner@rocketmail.com>
To: Theodore Tso <tytso@mit.edu>
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 12:47:12 +0100	[thread overview]
Message-ID: <9e520492-9b26-487f-9d60-7e0625c987c9@rocketmail.com> (raw)
In-Reply-To: <20260207175522.GB87551@macsyma.lan>

My review of our debate boils down to this UX image:

You provided excellent facts, articles, knowledge, and insights about
the design of systems around us. That is our reality frame -there is no
point in denying any of it.
That makes it a very powerful lever, a tool - let’s call it "a spoon",

Now, someone has a different dish on the table, and they really need
"a fork".
Instead of giving them the fork, we hand them a very powerful and rigid
spoon and say:
“Listen, here is a spoon. Try bending it a little and it should work!”

Someone comes forward with a fork, saying:
“Here is 'my fork'. I believe it may work well for 'some dishes'.”

I'm *really not* trying to bend the spoon here,
I *could* be asking if there is a spoon at all, but,
instead; I am simply showing you my fork, considering if it can be
helpful with some dishes.

 From that moment on, every discussion about "the spoon", of the
future and the past, condenses to this statement:
“Oh, 'the spoon' doesn’t work very well for you?
That’s fine - here's 'a fork'. Try using that for 'your dish'.”

Is the fork strictly essential? — maybe not, but it’s a valid option
that makes life a little easier for many of us.
Can you hurt yourself with a fork more easily? — maybe so; some care
and understanding are required
(hence disabled by default!)

Signing off,
manjo

If all you have is a hammer, everything looks like a nail.
(...fingernail included?!)

  parent reply	other threads:[~2026-02-08 11:47 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 ` 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 [this message]
2026-02-08 19:58                       ` Theodore Tso
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=9e520492-9b26-487f-9d60-7e0625c987c9@rocketmail.com \
    --to=mario_lohajner@rocketmail.com \
    --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=tytso@mit.edu \
    --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

all inboxes | Powered by JetHome®