From: James Bottomley <James.Bottomley@suse.de>
To: Andi Kleen <andi@firstfloor.org>
Cc: nab@linux-iscsi.org, linux-scsi@vger.kernel.org
Subject: Re: Full hostlock pushdown available
Date: Thu, 28 Oct 2010 14:28:43 -0500 [thread overview]
Message-ID: <1288294123.3043.164.camel@mulgrave.site> (raw)
In-Reply-To: <20101028150508.GA2385@basil.fritz.box>
On Thu, 2010-10-28 at 17:05 +0200, Andi Kleen wrote:
> Here's the promised attempt to do a full host_lock pushdown. This
> was done using coccinelle and some manual adjustments.
>
> This is just a dumb pushdown of host lock and serial number into
> the driver, no attempt to remove any locks yet.
>
> Currently lightly tested, but compiles with allmodconfig on 32bit x86.
>
> I made no attempt to automatically add maintainers to Cc.
>
> I'm not posting the patches because they are numerous and boring,
> but it's available in git.
>
> This will likely bitrot quickly so if it's decided to do it this
> way I would prefer if this was merged quickly.
OK, so can you post an actual diff? It obviously has to be done in one
commit rather than the 87 you have.
> Issues found:
> - I found a clear deadlock in aha1740, not sure if that driver ever
> worked since host_lock was introduced. Anyways I attempted to work
> around it. But if it's really that unused it may be better to
> simply drop it.
I certainly don't have the hardware ... and I don't think we've had any
bug reports for a while
> - I'm not sure how to compile cciss_scsi, is it even used?
It's used for tape support in the cciss driver. It's actually #included
into the cciss.c file (don't ask, I'll only start to cry) and is
conditioned on the CISS_SCSI_TAPE Kconfig variable.
James
next prev parent reply other threads:[~2010-10-28 19:28 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-28 15:05 Full hostlock pushdown available Andi Kleen
2010-10-28 19:28 ` James Bottomley [this message]
2010-10-28 19:32 ` Nicholas A. Bellinger
2010-11-01 14:06 ` Andi Kleen
2010-11-01 14:29 ` James Bottomley
2010-10-28 20:10 ` Andi Kleen
2010-10-28 20:22 ` James Bottomley
2010-10-28 21:50 ` Andi Kleen
2010-10-28 22:37 ` Nicholas A. Bellinger
2010-10-31 12:22 ` Boaz Harrosh
2010-10-31 18:48 ` Stefan Richter
2010-11-01 2:34 ` Jeff Garzik
2010-11-01 13:53 ` Andi Kleen
2010-11-01 15:56 ` Jeff Garzik
2010-11-01 17:57 ` Andi Kleen
2010-11-01 18:42 ` Jeff Garzik
2010-11-02 15:05 ` Andi Kleen
2010-11-01 18:59 ` Jeff Garzik
2010-11-01 21:06 ` Nicholas A. Bellinger
2010-11-02 9:21 ` Andi Kleen
2010-11-02 15:59 ` Jeff Garzik
2010-11-02 17:53 ` Andi Kleen
2010-11-02 18:13 ` Jeff Garzik
2010-11-02 18:38 ` Nicholas A. Bellinger
2010-11-02 18:50 ` Jeff Garzik
2010-11-01 13:54 ` Andi Kleen
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=1288294123.3043.164.camel@mulgrave.site \
--to=james.bottomley@suse.de \
--cc=andi@firstfloor.org \
--cc=linux-scsi@vger.kernel.org \
--cc=nab@linux-iscsi.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