All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@trained-monkey.org>
To: Adam Radford <aradford@3WARE.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>,
	Jens Axboe <axboe@suse.de>
Subject: Re: [patch] 3Ware 64 bit locking issues
Date: 22 Aug 2001 15:04:14 -0400	[thread overview]
Message-ID: <m3g0ajncgh.fsf@trained-monkey.org> (raw)
In-Reply-To: <53B208BD9A7FD311881A009027B6BBFB9EAE47@siamese>
In-Reply-To: Adam Radford's message of "Wed, 22 Aug 2001 11:48:07 -0700"

>>>>> "Adam" == Adam Radford <aradford@3WARE.com> writes:

Adam> Thanks for flags type fix and redundant pushf/popf fix.
Adam> Regarding your question about the error handling routines, the
Adam> 3ware driver uses the new style scsi error handling, so looking
Adam> through scsi_error.c, all calls to
Adam> hostt->eh_abort_handler() and hostt->eh_host_reset_handler() are
Adam> wrapped with a spin_lock_irqsave(&io_request_lock, flags) and
Adam> spin_unlock_irqrestore(&io_request_lock, flags) so they should
Adam> be okay.

Hmm ok. However, since Jens is working on killing the io_request_lock
so something will need to get done when that happens.

Jens, what is the strategy for that?

Cheers
Jes

       reply	other threads:[~2001-08-22 19:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <53B208BD9A7FD311881A009027B6BBFB9EAE47@siamese>
2001-08-22 19:04 ` Jes Sorensen [this message]
2001-08-23  6:59   ` [patch] 3Ware 64 bit locking issues Jens Axboe
2001-08-16  4:21 jes

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=m3g0ajncgh.fsf@trained-monkey.org \
    --to=jes@trained-monkey.org \
    --cc=aradford@3WARE.com \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.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.