All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: ric@emc.com
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-ide@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>,
	Mark Lord <mlord@pobox.com>
Subject: Re: error handling - DMA to PIO step down sequence
Date: Fri, 22 Sep 2006 01:58:53 +0900	[thread overview]
Message-ID: <4512C4CD.80000@gmail.com> (raw)
In-Reply-To: <4512C2C0.9010503@emc.com>

Ric Wheeler wrote:
> Alan Cox wrote:
>> Ar Iau, 2006-09-21 am 12:26 -0400, ysgrifennodd Ric Wheeler:
>>
>>>>> Would this be a reasonable thing for a config option? Better to add 
>>>>> yet another blacklist for devices that might have a justified need 
>>>>> for this derating?
>>
>> I think so. I've got "Adding a set of flags to blacklist entries" on my
>> todo list so that we can indicate and deal with different kinds of
>> horkage.
> 
> That could be very useful - flag specific drives to disable NCQ 
> (regardless of the internal setting for drive queue depth) and so on.

Yeap, in general, we need a blacklist.  For example, some drives only do 
NCQ w/ only 16 or so commands or others have completely broken NCQ 
support.  But I don't think the broken read log page 10h needs a 
blacklist entry.  It can be easily handled by good default behavior.

-- 
tejun

      reply	other threads:[~2006-09-21 16:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-20 19:03 error handling - DMA to PIO step down sequence Ric Wheeler
2006-09-21 15:09 ` Tejun Heo
2006-09-21 16:26   ` Ric Wheeler
2006-09-21 17:04     ` Alan Cox
2006-09-21 16:50       ` Ric Wheeler
2006-09-21 16:58         ` Tejun Heo [this message]

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=4512C4CD.80000@gmail.com \
    --to=htejun@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=mlord@pobox.com \
    --cc=ric@emc.com \
    /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.