From: Tejun Heo <htejun@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-ide@vger.kernel.org, Danny Kukawka <dkukawka@novell.com>,
Stefan Seyfried <seife@novell.com>
Subject: Re: [PATCH] libata: use FLUSH_EXT only when driver is larger than LBA28 limit
Date: Sat, 11 Nov 2006 03:44:05 +0900 [thread overview]
Message-ID: <4554C875.3000505@gmail.com> (raw)
In-Reply-To: <20061110183304.GA22793@htj.dyndns.org>
Tejun Heo wrote:
> Many drives support LBA48 even when its capacity is smaller than
> 1<<28, as LBA48 is required for many functionalities. FLUSH_EXT is
> mandatory for drives w/ LBA48 support.
>
> Interestingly, at least one of such drives (ST960812A) has problems
> dealing with FLUSH_EXT. It eventually completes the command but takes
> around 7 seconds to finish in many cases thus drastically slowing down
> IO transactions. This seems to be a firmware bug which sneaked into
> production probably because no other ATA driver including linux IDE
> issues FLUSH_EXT to drives which report support for LBA48 & FLUSH_EXT
> but is smaller than 1<<28 blocks.
>
> This patch adds ATA_DFLAG_FLUSH_EXT which is set iff the drive
> supports LBA48 & FLUSH_EXT and is larger than LBA28 limit. Both cache
> flush paths are updated to issue FLUSH_EXT only when the flag is set.
> Note that the changed behavior is more inline with the rest of libata.
> libata prefers shorter commands whenever possible.
Jeff, I think this should go into #uptream-fixes, too. We shouldn't
have issued FLUSH_EXT to < 1<<28 devices in the first place.
Thanks.
--
tejun
next prev parent reply other threads:[~2006-11-10 18:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 18:33 [PATCH] libata: use FLUSH_EXT only when driver is larger than LBA28 limit Tejun Heo
2006-11-10 18:44 ` Tejun Heo [this message]
2006-11-10 19:18 ` Stefan Seyfried
2006-11-11 11:10 ` [PATCH UPDATED] " Tejun Heo
2006-11-14 18:46 ` Jeff Garzik
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=4554C875.3000505@gmail.com \
--to=htejun@gmail.com \
--cc=dkukawka@novell.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=seife@novell.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).