From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Benjamin Marzinski <bmarzins@redhat.com>
Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>,
device-mapper development <dm-devel@lists.linux.dev>,
Martin Wilck <Martin.Wilck@suse.com>
Subject: Re: [PATCH 0/4] minio cleanup patches.
Date: Tue, 16 Jun 2026 09:47:09 +0200 [thread overview]
Message-ID: <50a665f3-8bcc-42bf-ab33-5cdafa70440b@gmail.com> (raw)
In-Reply-To: <ajCDBM2lH7NvcuX8@redhat.com>
On 6/16/26 12:56 AM, Benjamin Marzinski wrote:
> On Mon, Jun 15, 2026 at 11:00:48PM +0200, Xose Vazquez Perez wrote:
>> On 6/15/26 9:07 PM, Benjamin Marzinski wrote:
>>
>>> This patchset is to deprecate the rr_weight, rr_min_io_rq, and rr_min_io
>>> multipath config options. It's a companion of the patchset to handle
>>> their deprecation in the man pages.
>>> https://lore.kernel.org/all/20260607103831.336833-2-xose.vazquez@gmail.com/
>>>
>>> It does not completely remove the minio setting code, since there are
>>> ideas for reusing this in the future. The final patch is simply a change
>>> to avoid a kernel warning message that I hit while testing these
>>> patches.
>> Ben, thanks for this cleanup.
>>
>> I ran grep to see what remains of these options in the codebase.
>> Could you please check if any of the following occurrences should have been
>> removed, or if they are intended to stay for now?
>>
>> 8<---
>> $ git grep -Ei "rr_weight|minio|min_io" | grep -vE "multipath.conf.5.in|deprecated"
>>
>
> Good catch. It appears I misses some things.
I ran the following command to locate previous "deprecated keywords":
$ for i in $(git grep -h deprecated libmultipath/dict.c | grep install_keyword | sort | uniq | awk -F\" '{print $2}') ; do printf "\\n\n--- $i\n\n" ; git grep -i $i | grep -vE
"install_keyword|multipath.conf.5.in|\.md|deprecated_handler" ; done
It looks like there is some leftover code that could also be cleaned up, such as:
--- disable_changed_wwids
libmultipath/defaults.h:#define DEFAULT_DISABLE_CHANGED_WWIDS 1
and also some checks in tests/hwtable.c.
Could you please take a look at these as well?
Regards.
prev parent reply other threads:[~2026-06-16 7:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 19:07 [PATCH 0/4] minio cleanup patches Benjamin Marzinski
2026-06-15 19:07 ` [PATCH 1/4] libmultipath: deprecate rr_weight, and make it do nothing Benjamin Marzinski
2026-06-15 19:07 ` [PATCH 2/4] libmultipath: deprecate rr_min_io_rq, " Benjamin Marzinski
2026-06-15 19:07 ` [PATCH 3/4] libmultipath: deprecate rr_min_io Benjamin Marzinski
2026-06-15 19:07 ` [PATCH 4/4] libmultipath: don't set hwhander for bio based devices Benjamin Marzinski
2026-06-15 21:00 ` [PATCH 0/4] minio cleanup patches Xose Vazquez Perez
2026-06-15 22:56 ` Benjamin Marzinski
2026-06-16 7:47 ` Xose Vazquez Perez [this message]
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=50a665f3-8bcc-42bf-ab33-5cdafa70440b@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=Martin.Wilck@suse.com \
--cc=bmarzins@redhat.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-devel@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.