All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Andi Kleen <andi@firstfloor.org>,
	Stefan Richter <stefanr@s5r6.in-berlin.de>,
	Boaz Harrosh <bharrosh@panasas.com>,
	James.Bottomley@suse.de, nab@linux-iscsi.org,
	linux-scsi@vger.kernel.org,
	Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: Full hostlock pushdown available
Date: Tue, 2 Nov 2010 18:53:36 +0100	[thread overview]
Message-ID: <20101102175336.GA2167@basil.fritz.box> (raw)
In-Reply-To: <4CD03578.3050801@garzik.org>

> Boaz' approach is OBVIOUSLY mechanical, correct and bisectable.
> Yours is not.

Sorry Jeff, but my patch has 100% the same locking order as Boaz.
The only difference is in which function it is.

-Andi

  reply	other threads:[~2010-11-02 17:53 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
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 [this message]
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=20101102175336.GA2167@basil.fritz.box \
    --to=andi@firstfloor.org \
    --cc=James.Bottomley@suse.de \
    --cc=bharrosh@panasas.com \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@linux-iscsi.org \
    --cc=stefanr@s5r6.in-berlin.de \
    /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.