From: "Theodore Tso" <tytso@mit.edu>
To: Mario Lohajner <mario_lohajner@rocketmail.com>
Cc: Andreas Dilger <adilger@dilger.ca>,
libaokun1@huawei.com, adilger.kernel@dilger.ca,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
yangerkun@huawei.com, libaokun9@gmail.com
Subject: Re: [PATCH] ext4: rralloc - (former rotalloc) improved round-robin allocation policy
Date: Thu, 26 Feb 2026 20:12:00 -0500 [thread overview]
Message-ID: <20260227011200.GA68551@macsyma-wired.lan> (raw)
In-Reply-To: <04dfeda0-8c13-4233-b631-d8912d4fe6f0@rocketmail.com>
On Thu, Feb 26, 2026 at 10:50:29PM +0100, Mario Lohajner wrote:
> The primary purpose of rralloc is to improve allocation distribution
> and avoid hotspotting. Performance improvements are not the goal here...
You haven't explained *why* allocation distribution and avoiding
hotspotting is something we should care about.
If it's not performance, then why? How does reducing hotspotting
improve things for the user? Why should we care about this goal that
apparently is so important to you?
- Ted
next prev parent reply other threads:[~2026-02-27 1:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260225201520.220071-1-mario_lohajner.ref@rocketmail.com>
2026-02-25 20:15 ` [PATCH] ext4: rralloc - (former rotalloc) improved round-robin allocation policy Mario Lohajner
2026-02-25 23:49 ` Andreas Dilger
2026-02-26 2:48 ` Theodore Tso
2026-02-26 21:50 ` Mario Lohajner
2026-02-27 1:12 ` Theodore Tso [this message]
2026-02-27 14:46 ` Mario Lohajner
2026-02-27 16:43 ` Theodore Tso
2026-03-02 20:04 ` Mario Lohajner
2026-03-03 1:33 ` Theodore Tso
2026-03-03 13:28 ` Mario Lohajner
2026-03-05 2:47 ` Theodore Tso
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=20260227011200.GA68551@macsyma-wired.lan \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=adilger@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