public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Luben Tuikov <luben_tuikov@adaptec.com>
To: "Moore, Eric Dean" <Eric.Moore@lsil.com>
Cc: linux scsi <linux-scsi@vger.kernel.org>,
	James Bottomley <James.Bottomley@SteelEye.com>
Subject: Re: [PATCH] - mptfusion - adding back the spin locks in eh handle rs
Date: Thu, 23 Jun 2005 16:37:57 -0400	[thread overview]
Message-ID: <42BB1DA5.6000302@adaptec.com> (raw)
In-Reply-To: <91888D455306F94EBD4D168954A9457C02D506D4@nacos172.co.lsil.com>

On 06/23/05 16:12, Moore, Eric Dean wrote:
> Ok, explain that to me why having our driver hang is a good thing.
> The task managment requests to our firmware stack are done in interrupt
> mode,
> thus we have sleep and have interrupts enabled in the eh threads waiting on
> the commands to complete.
> Christoph H. requested this change about 6 months ago, asking that we remove
> our watchdog timers in the eh threads, in favor of this design.

Hi Eric,

It is up to the LLDD to know how to deliver a TMF to the device.
Whether this is done purely in process context (iSCSI) or
in mixed context is up to the LLDD.

Also, most often than not, you'd want to wait for the TMF to
return (iSCSI), to know its status (although you can assume it without fault).

Nevertheless, calling the eh routines in process context is the way
to go. (in order to allow for "sleeping", on delivery you can disable ints
as appropriate for the hw)

	Luben

  reply	other threads:[~2005-06-23 20:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-23 20:12 [PATCH] - mptfusion - adding back the spin locks in eh handle rs Moore, Eric Dean
2005-06-23 20:37 ` Luben Tuikov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-06-23 22:06 Moore, Eric Dean
2005-06-23 23:18 ` Jeff Garzik
2005-06-23 23:47 ` Luben Tuikov
2005-06-24 17:24 Moore, Eric Dean

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=42BB1DA5.6000302@adaptec.com \
    --to=luben_tuikov@adaptec.com \
    --cc=Eric.Moore@lsil.com \
    --cc=James.Bottomley@SteelEye.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox