linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Tejun Heo <htejun@gmail.com>,
	James Bottomley <James.Bottomley@HansenPartnership.com>,
	Jens Axboe <jens.axboe@oracle.com>,
	linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: Prevent busy looping
Date: Wed, 11 Jun 2008 08:05:02 +0100	[thread overview]
Message-ID: <20080611080502.4aa43980@core> (raw)
In-Reply-To: <484F7A8D.1040809@gmail.com>

> Elias's synthetic test case triggered infinite loop because it wasn't
> a proper ->qc_defer().  ->qc_defer() should never defer commands when
> the target is idle.

Target or host ? We *do* defer commands in the case of an idle channel
when dealing with certain simplex controllers that can only issue one
command per host not one per cable (and in fact in the general case we
can defer commands due to activity on the other drive on the cable).

Alan

  reply	other threads:[~2008-06-11  7:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080416151305.8788.63912.stgit@denkblock.local>
     [not found] ` <20080416163152.GK12774@kernel.dk>
     [not found]   ` <87r6d5l9pb.fsf@denkblock.local>
     [not found]     ` <20080417071335.GR12774@kernel.dk>
2008-04-17  8:50       ` Prevent busy looping Elias Oltmanns
2008-06-11  7:11         ` Tejun Heo
2008-06-11  7:05           ` Alan Cox [this message]
2008-06-11  8:03             ` Tejun Heo
2008-06-12  3:06               ` Tejun Heo
2008-06-12 11:32                 ` Elias Oltmanns
2008-06-12 13:43                   ` Tejun Heo
2008-06-12 14:18                     ` James Bottomley

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=20080611080502.4aa43980@core \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=htejun@gmail.com \
    --cc=jens.axboe@oracle.com \
    --cc=linux-ide@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).