From: Tejun Heo <htejun@gmail.com>
To: Ric Wheeler <ric@emc.com>
Cc: jeff@garzik.org, alan@lxorguk.ukuu.org.uk, edmudama@gmail.com,
linux-ide@vger.kernel.org, Mark Lord <mlord@pobox.com>
Subject: Re: asdf
Date: Sat, 03 Feb 2007 13:07:39 +0900 [thread overview]
Message-ID: <45C40A8B.1090307@gmail.com> (raw)
In-Reply-To: <45C36DED.9020809@emc.com>
Ric Wheeler wrote:
[--snip--]
> We might still want/need to be able to "lock" specific drives so that
> they do not drop out of DMA mode, not as the default but as a system
> tuning issue. What we see in the set of ATA drives that we have in the
> field is that dropping out of DMA mode is basically useless (for us at
> least) since it is so slow and we always have other drives to fall back
> on. Clearly not the case for typical end users, but a common case in the
> storage space where we pack as many disk drives into each box as we can.
I agree that some tuning knobs can be useful. SATA drives now never
drops to PIO mode due to errors. Even PATA drives should be failing
really hard to get degraded into PIO mode.
> On that other thread, I mentioned that we need to get some good testing
> done with this kind of thing. With Mark's error injection fixes (or the
> new ATA spec'ed ability to inject errors that Doug mentioned), along
> with our population of real world flaky drives, I hope to be able to
> beat on this in a realistic way in our labs,
Yeap, really. Things are pretty easy to adjust. With all the posted
patches applied...
* Errors are categorized by ata_eh_categorize_error() considering
whether the failed request was regular IO operation and the err_mask.
* ata_eh_speed_down_verdict() scans error history and determines
verdicts (or'd bitmask of ATA_EH_SPDN_* flags).
* ata_eh_speed_down() tries to apply the verdict. It always prefers the
least severe verdict and once a verdict is applied all others are
ignored and error history is cleared.
So, the basic tuning point is ata_eh_speed_down_verdict(). It's a very
short and easy-to-tune function which determines for how far back the
error history is scanned and which categories of errors trigger which
verdict.
Experimenting in realistic setup and reporting how the current setting
works and how better can it be adjusted will be a huge help.
Thanks.
--
tejun
prev parent reply other threads:[~2007-02-03 4:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 7:22 asdf Tejun Heo
2007-02-02 7:22 ` [PATCH 2/5] libata: improve probe failure handling Tejun Heo
2007-02-02 7:22 ` [PATCH 1/5] libata: improve ata_down_xfermask_limit() Tejun Heo
2007-02-20 15:46 ` Jeff Garzik
2007-02-02 7:22 ` [PATCH 3/5] libata: put some intelligence into EH speed down sequence Tejun Heo
2007-02-02 7:22 ` [PATCH 4/5] libata: kill ATA_DNXFER_ANY Tejun Heo
2007-02-02 7:22 ` [PATCH 5/5] ahci: consider SDB FIS containing spurious NCQ completions HSM violation Tejun Heo
2007-02-20 15:46 ` Jeff Garzik
2007-02-21 7:34 ` [PATCH 5/5] ahci: consider SDB FIS containing spurious NCQ completions HSM violation (regenerated) Tejun Heo
2007-02-23 10:37 ` Jeff Garzik
2007-02-02 7:24 ` Subject is [PATCH,RESEND] libata: put some intelligence into speed down sequence Tejun Heo
2007-02-02 16:59 ` asdf Ric Wheeler
2007-02-03 4:07 ` 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=45C40A8B.1090307@gmail.com \
--to=htejun@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=edmudama@gmail.com \
--cc=jeff@garzik.org \
--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 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).