From: James Smart <James.Smart@Emulex.Com>
To: "Moore, Eric" <Eric.Moore@lsil.com>
Cc: linux-scsi@vger.kernel.org, akpm@osdl.org,
James.Bottomley@SteelEye.com, hch@infradead.org
Subject: Re: [PATCH 2/5] - fusion - target reset when drive is being removed
Date: Thu, 26 Jan 2006 09:39:59 -0500 [thread overview]
Message-ID: <43D8DF3F.6090206@emulex.com> (raw)
In-Reply-To: <F331B95B72AFFB4B87467BE1C8E9CF5F1FED50@NAMAIL2.ad.lsil.com>
Interesting that you took this path. I'm working on something similar
for the FC transport. When we finally decide the device is gone, we
want to kill the outstanding i/o. First thought in my mind was to use
a TMF - but this implies that you can contact the device to do the TMF.
Are you sending this before the device has actually gone away ? If it's
after, I assume this then is a firmware function that handles things
accordingly at the link layer (e.g. may not send the TMF, will internally
abort the outstanding io's, may note the TR request and do it when the
device is later detected.... and so on).
Can you comment ?
-- james
Moore, Eric wrote:
> The issuing of the target reset
> used in device hot removal case so the
> firmware queue is flushed out off outstanding
> commands.
>
> Signed-off-by: Eric Moore <Eric.Moore@lsil.com>
next prev parent reply other threads:[~2006-01-26 14:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 1:05 [PATCH 2/5] - fusion - target reset when drive is being removed Moore, Eric
2006-01-26 14:39 ` James Smart [this message]
2006-01-26 19:37 ` Christoph Hellwig
-- strict thread matches above, loose matches on Subject: below --
2006-01-26 15:07 Moore, Eric
2006-01-26 15:14 ` James Smart
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=43D8DF3F.6090206@emulex.com \
--to=james.smart@emulex.com \
--cc=Eric.Moore@lsil.com \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--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.