From: Tejun Heo <htejun@gmail.com>
To: jeff@garzik.org, linux-ide@vger.kernel.org
Subject: [PATCHSET] libata: update EH speed down logic
Date: Fri, 2 Nov 2007 00:51:36 +0900 [thread overview]
Message-ID: <11939323042554-git-send-email-htejun@gmail.com> (raw)
Hello,
This patchset updates EH speed down logic such that...
* Speed down rules are less conservative. For example, falling back
to PIO was triggered if there have been more than 10 ATA_BUS,
TOUT_HSM or UNK_DEV in 5 minutes. However, 11 timeouts can't happen
in five minutes as each timeout is 30 secs long.
* Consecutive errors occurring right after data transfer mode (NCQ
on/off and xfermode) has been changed trigger fast back-to-back
speed downs. This helps libata EH find the correct transfer mode
faster such that the user is bored less and higher level probing
(partition scanning) doesn't fail.
This patchset contains 8 patches. The first five prepare for speed
down logic update. The 6th one relaxes existing speed down rules.
The last two implement fast speed down after transfer mode change.
This patchset is on top of update-EH-configurat-behavior patchset[1].
Thanks.
--
tejun
[1] http://thread.gmane.org/gmane.linux.ide/24281
next reply other threads:[~2007-11-01 15:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 15:51 Tejun Heo [this message]
2007-11-01 15:51 ` [PATCH 1/8] libata: rearrange ATA_DFLAG_* Tejun Heo
2007-11-01 15:51 ` [PATCH 2/8] libata: add protocol data transfer tests Tejun Heo
2007-11-01 15:51 ` [PATCH 3/8] libata: factor out ata_eh_schedule_probe() Tejun Heo
2007-11-01 15:51 ` [PATCH 4/8] libata: move ata_set_mode() to libata-eh.c Tejun Heo
2007-11-01 15:51 ` [PATCH 5/8] libata: clean up EH speed down implementation Tejun Heo
2007-11-01 15:51 ` [PATCH 6/8] libata: adjust speed down rules Tejun Heo
2007-11-01 15:51 ` [PATCH 7/8] libata: implement ATA_DFLAG_DUBIOUS_XFER Tejun Heo
2007-11-01 15:51 ` [PATCH 8/8] libata: implement fast speed down for unverified data transfer mode Tejun Heo
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=11939323042554-git-send-email-htejun@gmail.com \
--to=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@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).