linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Jianlin Lv <iecedge@gmail.com>,
	jejb@linux.ibm.com, martin.petersen@oracle.com,
	paulmck@kernel.org, bp@suse.de, peterz@infradead.org,
	will@kernel.org, rdunlap@infradead.org, kim.phillips@amd.com,
	rostedt@goodmis.org, wyes.karny@amd.com
Cc: jianlv@ebay.com, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: sd: support specify probe type of build-in driver
Date: Tue, 6 Jun 2023 10:38:25 -0700	[thread overview]
Message-ID: <6ad5fba3-926a-7a23-b21b-abffd33708be@acm.org> (raw)
In-Reply-To: <20230606051217.2064-1-iecedge@gmail.com>

On 6/5/23 22:12, Jianlin Lv wrote:
> In scenarios where SCSI disk name sensitivity is crucial, the probe type
> of the build-in sd driver can be set to synchronous. As a result,
> the scsi disk names are deterministic.

Which are these scenarios?

Additionally, how can synchronous scanning of sd devices make a 
difference if there are multiple host bus adapters that use an interface 
type that is scanned asynchronously?

Bart.

  reply	other threads:[~2023-06-06 17:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-06  5:12 [PATCH] scsi: sd: support specify probe type of build-in driver Jianlin Lv
2023-06-06 17:38 ` Bart Van Assche [this message]
2023-06-07 15:55   ` Jianlin Lv
2023-06-07 17:07     ` Bart Van Assche
2023-06-08  2:51       ` Jianlin Lv
2023-06-08 16:23         ` Bart Van Assche
2023-06-24 11:45           ` Jianlin Lv
2023-06-07 14:10 ` Christoph Hellwig
2023-06-08  3:10   ` Jianlin Lv

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=6ad5fba3-926a-7a23-b21b-abffd33708be@acm.org \
    --to=bvanassche@acm.org \
    --cc=bp@suse.de \
    --cc=iecedge@gmail.com \
    --cc=jejb@linux.ibm.com \
    --cc=jianlv@ebay.com \
    --cc=kim.phillips@amd.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rdunlap@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=will@kernel.org \
    --cc=wyes.karny@amd.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;
as well as URLs for NNTP newsgroup(s).