Linux Device Mapper development
 help / color / mirror / Atom feed
From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: Martin Wilck <mwilck@suse.com>, Benjamin Marzinski <bmarzins@redhat.com>
Cc: Christophe Varoqui <christophe.varoqui@opensvc.com>,
	device-mapper development <dm-devel@lists.linux.dev>
Subject: Obsolete features (was Re: [PATCH 0/4] minio cleanup patches.)
Date: Sun, 19 Jul 2026 16:57:00 +0200	[thread overview]
Message-ID: <467670f5-2a5e-4051-9d24-eafa15e2f565@gmail.com> (raw)
In-Reply-To: <50a665f3-8bcc-42bf-ab33-5cdafa70440b@gmail.com>

On 6/16/26 9:47 AM, Xose Vazquez Perez wrote:

> 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.
Is this still necessary in "write_defaults : tests/hwtable.c" ?

                { "bindings_file", NULL },
                { "config_dir", NULL },
                { "multipath_dir", NULL },


Another candidate to drop is the retain_attached_hw_handler infrastructure:
  ( grep -Eir "hwhandler|hw_handler" )
Since Linux 4.3, the kernel always enforces "retain_attached_hw_handler yes".
Because this option is completely obsolete, could it be dropped from multipath-tools?


Regards.

  reply	other threads:[~2026-07-19 14:57 UTC|newest]

Thread overview: 11+ 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
2026-07-19 14:57       ` Xose Vazquez Perez [this message]
2026-07-20 15:33         ` Obsolete features (was Re: [PATCH 0/4] minio cleanup patches.) Benjamin Marzinski
2026-07-20 19:29           ` Martin Wilck

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=467670f5-2a5e-4051-9d24-eafa15e2f565@gmail.com \
    --to=xose.vazquez@gmail.com \
    --cc=bmarzins@redhat.com \
    --cc=christophe.varoqui@opensvc.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=mwilck@suse.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