linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zheng Liu <gnehzuil.liu@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Robert Hancock <hancockrwd@gmail.com>,
	linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
	linux-scsi@vger.kernel.org, Jeff Garzik <jeff@garzik.org>,
	Zheng Liu <wenqing.lz@taobao.com>
Subject: Re: [RFC][PATCH] libata: enable SATA disk fua detection on default
Date: Wed, 9 May 2012 17:30:16 +0800	[thread overview]
Message-ID: <20120509093016.GA12754@gmail.com> (raw)
In-Reply-To: <20120509082527.GA10674@infradead.org>

On Wed, May 09, 2012 at 04:25:27AM -0400, Christoph Hellwig wrote:
> On Wed, May 09, 2012 at 02:19:56PM +0800, Zheng Liu wrote:
> > disable FUA detection for SATA disk.  If FUA feature can be used, we
> > could disable io_barrier to improve the performance.  Now one solution
> 
> You can't run with -o nobarrier just because the driver/hardware support
> FUA.  However the implementation of -o barrier (aka REQ_FUA) is a lot
> more efficient if it is implemented.  If your workload has a high
> percentage of REQ_FUA requests it might be better to switch the disks to
> write through mode entirely.

Thanks for your advice.  Indeed, it is more efficient when data is
flushed with REQ_FUA, and this is the reason why I submit this patch.
IMHO, FUA provides a solution that we can get better performance in write
cache mode when we do many flush operations.  If I set the disk to write
through mode, I won't get this benefit.  Am I missing something?

Currently, the key issue is that we disable FUA detection for SATA disk.
We almost have no chance to change it because it is too complicated to
set libata_fua variable when this module is loaded.  So why not give
SATA disk an opportunity to enable this feature?  After all, there is a
lot of SATA disks that support this feature.

Regards,
Zheng

  reply	other threads:[~2012-05-09  9:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-08  3:24 [RFC][PATCH] libata: enable SATA disk fua detection on default Zheng Liu
2012-05-09  5:38 ` Robert Hancock
2012-05-09  6:19   ` Zheng Liu
2012-05-09  8:25     ` Christoph Hellwig
2012-05-09  9:30       ` Zheng Liu [this message]
2012-05-09 11:12         ` Christoph Hellwig
2012-05-09 12:48           ` Zheng Liu
2012-05-09 13:20             ` Bernd Schubert
2012-05-09 13:23             ` Christoph Hellwig
2012-07-03  9:04 ` Zheng Liu
2012-07-03 20:11   ` Michael Tokarev
2012-07-04  2:47     ` Zheng Liu
2012-07-04  6:36       ` Michael Tokarev
2012-07-04  7:06         ` Zheng Liu
2012-09-09 20:34           ` Arvydas Sidorenko
2012-09-09 20:39             ` Jeff Garzik
2012-08-17 18:06 ` Enabling FUA for SATA drives (was Re: [RFC][PATCH] libata: enable SATA disk fua detection on default) 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=20120509093016.GA12754@gmail.com \
    --to=gnehzuil.liu@gmail.com \
    --cc=hancockrwd@gmail.com \
    --cc=hch@infradead.org \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=wenqing.lz@taobao.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).