public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: Bart Van Assche <bvanassche@acm.org>, <jejb@linux.vnet.ibm.com>,
	<martin.petersen@oracle.com>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] scsi: Delete scsi_use_blk_mq
Date: Tue, 11 Feb 2020 11:53:04 +0000	[thread overview]
Message-ID: <ca2a7eee-0456-e158-307d-e9b6f32fbefd@huawei.com> (raw)
In-Reply-To: <2e2ead7d-503e-3881-b837-7c689a4d44c6@huawei.com>

On 11/02/2020 11:50, John Garry wrote:
> On 10/02/2020 22:37, Bart Van Assche wrote:
>> On 2/10/20 9:33 AM, John Garry wrote:
>>> -module_param_named(use_blk_mq, scsi_use_blk_mq, bool, S_IWUSR | 
>>> S_IRUGO);
>>
> 
> Hi Bart,
> 
>> Will this change cause trouble to shell scripts that set or read this 
>> parameter (/sys/module/scsi_mod/parameters/use_blk_mq)? 
> 
> The entry in Documentation/admin-guide/kernel-parameters.txt is gone for 
> 2 years now.
> 
> And it is not an archaic module param, it was introduced 6 years ago. As 
> such, I'd say that if a shell script was setup to access this parameter, 
> then it would prob also pre-check if it exists and gracefully accept 
> that it may not.
> 
> I will also note that there is still scsi_sysfs.c:show_use_blk_mq(), 
> which would stay.
> 
> What will the
>> impact be on systems where scsi_mod.use_blk_mq=Y is passed by GRUB to 
>> the kernel at boot time, e.g. because it has been set in the 
>> GRUB_CMDLINE_LINUX variable in /etc/default/grub?
> 
> The kernel should any params that does not recognize.

	          ^ ignore

> 
>>
> 
> Having said all that, I don't feel too strongly about deleting this - 
> it's only some tidy-up.
> 
> Thanks,
> John
> 
> .


  reply	other threads:[~2020-02-11 11:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-10 17:33 [PATCH] scsi: Delete scsi_use_blk_mq John Garry
2020-02-10 22:37 ` Bart Van Assche
2020-02-11 11:50   ` John Garry
2020-02-11 11:53     ` John Garry [this message]
2020-02-12 16:10     ` Ewan D. Milne
2020-02-13  4:01 ` Martin K. Petersen

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=ca2a7eee-0456-e158-307d-e9b6f32fbefd@huawei.com \
    --to=john.garry@huawei.com \
    --cc=bvanassche@acm.org \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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