From: Tejun Heo <htejun@gmail.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Mark Lord <liml@rtr.ca>, Matthew Wilcox <matthew@wil.cx>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeff Garzik <jeff@garzik.org>
Subject: Re: ata_ram driver
Date: Fri, 07 Mar 2008 09:13:06 +0900 [thread overview]
Message-ID: <47D08892.3080209@gmail.com> (raw)
In-Reply-To: <1204848119.3062.94.camel@localhost.localdomain>
James Bottomley wrote:
>> * Driver unload: Dealt the same way as hot unplugging.
>
> This is the problem case: driver unloading should have a
> scsi_remove_host() in its path. This is the trigger that sends out the
> flushes/stops and calls slave_destroy. scsi_remove_host() doesn't
> actually return until all the destroys are completed, so it makes module
> unloading wait until everything is properly shut down.
>
>> Making driver unload like explicit unplug request is possible but it
>> will mean that drives will be spun down on driver unload, which can be
>> annoying to developers.
>
> You have a sysfs flag to prevent that, don't you?
Yeap, sure. It's the combination of things that always made me put this
off. Is there a function I can call to just shutdown the host instead
of destroying it?
Thanks.
--
tejun
next prev parent reply other threads:[~2008-03-07 0:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 20:09 ata_ram driver Matthew Wilcox
2008-02-22 21:27 ` Mark Lord
2008-03-06 8:21 ` Tejun Heo
2008-03-06 15:28 ` James Bottomley
2008-03-06 23:55 ` Tejun Heo
2008-03-07 0:01 ` James Bottomley
2008-03-07 0:13 ` Tejun Heo [this message]
2008-03-07 0:22 ` James Bottomley
2008-03-07 0:28 ` Tejun Heo
2008-03-07 0:39 ` James Bottomley
2008-03-07 0:43 ` Tejun Heo
2008-03-07 3:08 ` [PATCH 1/2] scsi: export scsi_forget_host() Tejun Heo
2008-03-07 3:11 ` [PATCH 2/2] libata: kill SCSI devices before detaching ata_host Tejun Heo
2008-03-07 2:16 ` ata_ram driver Jeff Garzik
2008-03-07 2:44 ` James Bottomley
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=47D08892.3080209@gmail.com \
--to=htejun@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jeff@garzik.org \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
/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).