From: illofspeed <illofspeed@gmail.com>
To: dlemoal@kernel.org
Cc: dm-devel@lists.linux.dev, agk@redhat.com, snitzer@kernel.org,
mpatocka@redhat.com, bmarzins@redhat.com, hare@suse.de,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] dm zoned: do not reclaim a random zone into another random zone
Date: Sun, 11 Oct 2026 18:17:33 +0200 [thread overview]
Message-ID: <20261011161733.404-1-illofspeed@gmail.com> (raw)
In-Reply-To: <d4adf5de-9d72-4977-b4c0-3e1f163872a1@kernel.org>
Damien Le Moal wrote:
>> + * Without a free sequential zone, moving a cache zone into a random
>> + * zone of the zoned device still frees cache space. Moving a random
>> + * zone into another random zone gains nothing, and when the target
>> + * is idle it repeats forever. Only fall back for cache zones.
>
> "fall back" to what? This comment is not clear.
To a random destination zone: the switch from DMZ_ALLOC_SEQ to
DMZ_ALLOC_RND just below. v3 rewords it:
/*
* If no free sequential zone is available, a cache zone can still be
* moved into a free random zone of the zoned device, which frees cache
* space. Do not do this for a random zone: moving it into another
* random zone frees nothing and, on an idle target, repeats forever.
*/
>> + if (!szone && alloc_flags == DMZ_ALLOC_SEQ && dmz_nr_cache_zones(zmd) &&
>
> Long line. Please split after "DMZ_ALLOC_SEQ &&".
> Also, is the test for dmz_nr_cache_zones() needed? dmz_is_cache(dzone) will
> never be true if there are no cache zones.
You are right: DMZ_CACHE is only set on zones of the regular device, so
the test is redundant. Without it the condition fits on one line:
if (!szone && alloc_flags == DMZ_ALLOC_SEQ && dmz_is_cache(dzone)) {
With this change the reproducer from the cover letter still shows 0 MB/s
on the idle target. I will send v3 once the Signed-off-by question on
1/3 is settled; patches 1 and 3 stay unchanged.
illofspeed
next prev parent reply other threads:[~2026-10-11 16:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 16:16 [PATCH v2 0/3] dm zoned: fix two idle reclaim problems illofspeed
2026-10-10 16:16 ` [PATCH v2 1/3] dm zoned: back off when reclaim finds no destination zone illofspeed
2026-10-11 14:24 ` Damien Le Moal
2026-10-11 16:17 ` illofspeed
2026-10-11 16:32 ` Damien Le Moal
2026-10-11 16:47 ` Damien Le Moal
2026-10-10 16:16 ` [PATCH v2 2/3] dm zoned: do not reclaim a random zone into another random zone illofspeed
2026-10-11 14:30 ` Damien Le Moal
2026-10-11 16:17 ` illofspeed [this message]
2026-10-10 16:16 ` [PATCH v2 3/3] dm zoned: keep polling for idle reclaim after a reclaim pass illofspeed
2026-10-11 14:31 ` Damien Le Moal
2026-10-11 16:17 ` illofspeed
2026-10-11 14:23 ` [PATCH v2 0/3] dm zoned: fix two idle reclaim problems Damien Le Moal
2026-10-11 14:33 ` Damien Le Moal
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=20261011161733.404-1-illofspeed@gmail.com \
--to=illofspeed@gmail.com \
--cc=agk@redhat.com \
--cc=bmarzins@redhat.com \
--cc=dlemoal@kernel.org \
--cc=dm-devel@lists.linux.dev \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=snitzer@kernel.org \
/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®