From: Jeff Garzik <jeff@garzik.org>
To: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [RFC] enable FUA support in libata
Date: Fri, 13 Apr 2012 10:18:32 -0400 [thread overview]
Message-ID: <4F8835B8.2060400@garzik.org> (raw)
In-Reply-To: <20120413081104.GA4953@gmail.com>
On 04/13/2012 04:11 AM, Zheng Liu wrote:
> Hi Jeff and list,
>
> Recently I met a problem about FUA support of SATA disk. In my machine,
> it has a SATA disk that supports FUA feature. But after system starts
> up, it displays that the disk cannot support FUA from dmesg.
>
> I notice this commit (c3c013a2). It disables FUA support in all of SATA
> disk. But the commit log is too simple to know why we should disable
> FUA support in libata. Could you please explain it? Thank you.
FUA support in the block layer wanted speed and guarantees that early
FUA drives were simply not providing.
next prev parent reply other threads:[~2012-04-13 14:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 8:11 [RFC] enable FUA support in libata Zheng Liu
2012-04-13 14:18 ` Jeff Garzik [this message]
2012-04-13 15:25 ` Zheng Liu
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=4F8835B8.2060400@garzik.org \
--to=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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