From: Tejun Heo <htejun@gmail.com>
To: Mark Lord <liml@rtr.ca>
Cc: jozwicki <jozwicki@aster.pl>,
jgarzik@pobox.com, linux-ide@vger.kernel.org, mingo@elte.hu
Subject: Re: spurious completions during NCQ on rt kernel
Date: Wed, 28 Nov 2007 09:37:42 +0900 [thread overview]
Message-ID: <474CB856.6060807@gmail.com> (raw)
In-Reply-To: <474A4C7B.1060804@rtr.ca>
Hello,
Mark Lord wrote:
> Mmmm.. that's interesting. I suppose a big difference between -rt and
> vanilla
> is in latency between interrupt signal and the interrupt handler
> actually running.
>
> I think in -rt it is slightly *longer*, since the handler is run by a
> scheduled
> thread instead of directly.
>
> Anyway, for me, the intriguing point of data here, is that there could
> be some
> tight soft timing issue that sometimes can make NCQ fail. And our
> response to date
> with this is to blacklist the drives.. which may or may not be correct now.
I think it's interrupt timing problem too. I just received my order of
problematic drives. I'll try to reproduce it and find out. At any
rate, I think we'll probably have to drop spurious NCQ completion check.
Thanks.
--
tejun
prev parent reply other threads:[~2007-11-28 0:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-24 23:14 spurious completions during NCQ on rt kernel jozwicki
2007-11-26 4:32 ` Mark Lord
2007-11-28 0:37 ` 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=474CB856.6060807@gmail.com \
--to=htejun@gmail.com \
--cc=jgarzik@pobox.com \
--cc=jozwicki@aster.pl \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=mingo@elte.hu \
/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.