From: Patrick Mansfield <patmans@us.ibm.com>
To: James.Smart@Emulex.Com
Cc: James.Bottomley@SteelEye.com, linux-scsi@vger.kernel.org,
hch@infradead.org, andmike@us.ibm.com, mort@wildopensource.com,
andrew.vasquez@qlogic.com
Subject: Re: [PATCH] [Update #2] suspending I/Os to a device
Date: Fri, 1 Oct 2004 09:02:09 -0700 [thread overview]
Message-ID: <20041001160208.GA22903@beaverton.ibm.com> (raw)
In-Reply-To: <0B1E13B586976742A7599D71A6AC733C02F1EA@xbl3.ma.emulex.com>
On Fri, Oct 01, 2004 at 09:54:53AM -0400, James.Smart@Emulex.Com wrote:
> +/**
> + * fc_host_block - block all scsi devices managed by the calling host temporarily
> + * by putting each device in the SDEV_BLOCK state.
> + * @shost: scsi host pointer that contains all scsi device siblings.
> + *
> + * scsi lld's with a FC transport call this routine to temporarily stop all
> + * scsi commands to all devices managed by this host. Called
> + * from interrupt or normal process context.
> + *
> + * Returns zero if successful or error if not
> + *
> + * Notes:
> + * The timeout and timer types are extracted from the fc transport
> + * attributes from the caller's host pointer. This routine assumes no
> + * locks are held on entry.
> + **/
> +int
> +fc_host_block(struct Scsi_Host *shost)
What is the difference between these new fc_host_block/unblock and
the current scsi_block/unblock_requests?
-- Patrick Mansfield
next prev parent reply other threads:[~2004-10-01 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-01 13:54 [PATCH] [Update #2] suspending I/Os to a device James.Smart
2004-10-01 16:02 ` Patrick Mansfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-01 16:21 James.Smart
2004-10-01 16:15 James.Smart
2004-09-30 20:57 James.Smart
2004-09-30 21:40 ` 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=20041001160208.GA22903@beaverton.ibm.com \
--to=patmans@us.ibm.com \
--cc=James.Bottomley@SteelEye.com \
--cc=James.Smart@Emulex.Com \
--cc=andmike@us.ibm.com \
--cc=andrew.vasquez@qlogic.com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mort@wildopensource.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