lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100823164522.GA9528@atlas.home>
Date:	Mon, 23 Aug 2010 20:45:22 +0400
From:	Sergey Vlasov <vsu@...linux.ru>
To:	Ric Wheeler <rwheeler@...hat.com>
Cc:	Jens Axboe <jaxboe@...ionio.com>, "tytso@....edu" <tytso@....edu>,
	"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
	"linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org>,
	"jack@...e.cz" <jack@...e.cz>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"swhiteho@...hat.com" <swhiteho@...hat.com>,
	"linux-raid@...r.kernel.org" <linux-raid@...r.kernel.org>,
	"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
	"dm-devel@...hat.com" <dm-devel@...hat.com>,
	"James.Bottomley@...e.de" <James.Bottomley@...e.de>,
	"konishi.ryusuke@....ntt.co.jp" <konishi.ryusuke@....ntt.co.jp>,
	Tejun Heo <tj@...nel.org>, "vst@...b.net" <vst@...b.net>,
	Christoph Hellwig <hch@....de>,
	"chris.mason@...cle.com" <chris.mason@...cle.com>
Subject: Re: [dm-devel] [PATCHSET block#for-2.6.36-post] block: replace
 barrier with sequenced flush

On Mon, Aug 23, 2010 at 11:19:13AM -0400, Ric Wheeler wrote:
[...]
> (2) hardware raid cards with internal buffer memory and on-card battery backup 
> (they sit in your server, disks sit in jbod like expansion shelves). These are 
> fine if the drives in those shelves have write cache disabled.

Actually some of such cards keep write cache on the drives enabled and
issue FLUSH CACHE commands to the drives.  E.g., 3ware 9690SA behaves
like this at least with SATA drives (the FLUSH CACHE commands can be
seen after enabling performance monitoring - they often end up in the
"10 commands having the largest latency" table).  This can actually be
safe if the card waits for the FLUSH CACHE completion before making
the write cache data in its battery-backed memory available for reuse
(and the drive implements the FLUSH CACHE command correctly).

Download attachment "signature.asc" of type "application/pgp-signature" (199 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ