mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: <jejb@linux.ibm.com>, <martin.petersen@oracle.com>,
	<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<kashyap.desai@broadcom.com>, <dgilbert@interlog.com>
Subject: Re: [PATCH] scsi: core: Cap initial sdev queue depth at shost.can_queue
Date: Thu, 22 Apr 2021 17:35:42 +0100	[thread overview]
Message-ID: <186be6c5-dbcd-d1fb-67c5-72b5a761568a@huawei.com> (raw)
In-Reply-To: <YIDTlD2Mq+U36Oqz@T590>

On 22/04/2021 02:38, Ming Lei wrote:
>> I would rather not change the values which are provided from the driver. I
>> would rather take the original values and try to use them in a sane way.
>>
>> I have not seen other places where driver shost config values are modified
>> by the core code.

Hi Ming,

> Wrt. .cmd_per_lun, I think it is safe to modify it into one correct
> depth because almost all drivers are just producer of .cmd_per_lun. And
> except for debug purpose, there are only three consumers of .cmd_per_lun
> in scsi, and all are for scsi_change_queue_depth():
> 
> 	process_message()
> 	scsi_alloc_sdev()
> 	virtscsi_change_queue_depth()

sg_ioctl_common() also looks to read it, but I can't imagine we could 
break that interface with either suggested change.

So I still prefer not to modify shost.cmd_per_lun, but if you feel 
strongly enough then I can look to make that change.

Thanks,
John


  reply	other threads:[~2021-04-22 16:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19 16:06 John Garry
2021-04-20  0:02 ` Ming Lei
2021-04-20  8:14   ` John Garry
2021-04-22  1:38     ` Ming Lei
2021-04-22 16:35       ` John Garry [this message]
2021-04-23  1:54         ` Ming Lei

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=186be6c5-dbcd-d1fb-67c5-72b5a761568a@huawei.com \
    --to=john.garry@huawei.com \
    --cc=dgilbert@interlog.com \
    --cc=jejb@linux.ibm.com \
    --cc=kashyap.desai@broadcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=ming.lei@redhat.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

all inboxes | Powered by JetHome®