From: Maurizio Lombardi <mlombard-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: loody <miloody-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
SCSI development list
<linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: Some question about usb scsi storage driver
Date: Fri, 04 Jul 2014 17:47:28 +0200 [thread overview]
Message-ID: <53B6CC90.4070805@redhat.com> (raw)
In-Reply-To: <CANudz+sXH55BJDWf3zy18ERixQWDnqtfv7GHmHPsqqJG9EGyxg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 07/04/2014 04:44 PM, loody wrote:
>
> 2. at the end of sd.c -> sd_probe, why we call async_schedule_domain like below
> async_schedule_domain(sd_probe_async, sdkp, &scsi_sd_probe_domain);
> to finish scsi device initialization?
> Couldn't we put what sd_probe_async directly in sd_probe?
> is there any benefit to do so?
A possible explanation may be that sd_probe_async() calls sd_spinup_disk(), this function spins up the drive and
may block for some seconds, so it is better to do that asynchronously.
Regards,
Maurizio Lombardi
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-07-04 15:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 14:44 Some question about usb scsi storage driver loody
[not found] ` <CANudz+sXH55BJDWf3zy18ERixQWDnqtfv7GHmHPsqqJG9EGyxg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-07-04 15:47 ` Maurizio Lombardi [this message]
2014-07-04 16:35 ` Alan Stern
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=53B6CC90.4070805@redhat.com \
--to=mlombard-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-scsi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-usb-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=miloody-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
/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