public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: James Bottomley <James.Bottomley@suse.de>
Cc: Andi Kleen <andi@firstfloor.org>,
	nab@linux-iscsi.org, linux-scsi@vger.kernel.org
Subject: Re: Full hostlock pushdown available
Date: Thu, 28 Oct 2010 23:50:17 +0200	[thread overview]
Message-ID: <20101028215017.GB2797@basil.fritz.box> (raw)
In-Reply-To: <1288297365.10498.4.camel@mulgrave.site>

> To put this upstream, I need the single commit (with changelog and
> signoff).  Otherwise the series won't bisect.  Murphys law says that if
> I apply an unbisectable series like this, all the kernel bisections in
> the next few months will end up in here, and I'll take a huge amount of
> flack ...

I expect even without the locking it should be safe enough for a bisect
test. Not for production of course. And most drivers don't really
need the lock anyways so they are safe in any case.

An alternative would be to use a different lock around the call
temporary during the series and drop it again at the end.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.

  reply	other threads:[~2010-10-28 21:50 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
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 [this message]
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=20101028215017.GB2797@basil.fritz.box \
    --to=andi@firstfloor.org \
    --cc=James.Bottomley@suse.de \
    --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