From: Nathan Bryant <nbryant@optonline.net>
To: "Ely, Paul" <Paul.Ely@Emulex.Com>
Cc: 'Christoph Hellwig' <hch@infradead.org>,
"Smart, James" <James.Smart@Emulex.Com>,
'James Bottomley' <James.Bottomley@steeleye.com>,
Linux SCSI Reflector <linux-scsi@vger.kernel.org>
Subject: Re: suspending I/Os to a device
Date: Fri, 23 Jul 2004 00:36:03 -0400 [thread overview]
Message-ID: <410095B3.8060902@optonline.net> (raw)
In-Reply-To: <3356669BBE90C448AD4645C843E2BF28025AB79F@xbl.ma.emulex.com>
Ely, Paul wrote:
>All,
>
>
>The following patch provides an implementation of
>the proposal contained in this mail thread. The
>patch does not provide a complete solution such
>as:
> nodevice tmo handling by the scsi midlayer
> scsi_device structure member for nodevice tmo
> handling of SDEV_SUSPEND state by midlayer
>
>Subsequent patches to address remaining implementation.
>
I'm a little late to the party. Is this intended to facilitate the PCI
power management (queue quiesce) issues that were discussed this week?
Will it be sufficient to "just call" these from pcidev->suspend(),
pcidev->resume()?
Duh, like thanks and stuff. I think.
Nathan
next prev parent reply other threads:[~2004-07-23 4:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-22 20:16 suspending I/Os to a device Ely, Paul
2004-07-23 4:36 ` Nathan Bryant [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-06 19:36 Paul.Ely
2004-08-02 21:22 Ely, Paul
2004-07-28 16:19 Ely, Paul
2004-07-26 19:11 Ely, Paul
2004-07-28 14:41 ` James Bottomley
2004-07-23 13:26 Ely, Paul
2004-07-19 20:04 Ely, Paul
2004-07-12 20:53 Ely, Paul
2004-07-17 12:24 ` Christoph Hellwig
2004-05-05 19:00 Smart, James
2004-04-26 17:12 Infante, Jon
2004-04-26 21:26 ` 'Patrick Mansfield'
2004-04-23 22:12 Infante, Jon
2004-04-23 23:28 ` James Bottomley
2004-04-26 16:40 ` Patrick Mansfield
2004-04-23 16:28 Ely, Paul
2004-04-23 15:59 Infante, Jon
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=410095B3.8060902@optonline.net \
--to=nbryant@optonline.net \
--cc=James.Bottomley@steeleye.com \
--cc=James.Smart@Emulex.Com \
--cc=Paul.Ely@Emulex.Com \
--cc=hch@infradead.org \
--cc=linux-scsi@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.