From: Greg KH Subject: Re: [PATCH 5 of 7] block: Block/request layer data integrity support Date: Sat, 7 Jun 2008 21:27:54 -0700 Message-ID: <20080608042754.GA21251@kroah.com> References: <5be7c534c9542dc4bab1.1212814538@sermon.lab.mkp.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from pentafluge.infradead.org ([213.146.154.40]:37962 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750783AbYFHEbP (ORCPT ); Sun, 8 Jun 2008 00:31:15 -0400 Content-Disposition: inline In-Reply-To: <5be7c534c9542dc4bab1.1212814538@sermon.lab.mkp.net> Sender: linux-scsi-owner@vger.kernel.org List-Id: linux-scsi@vger.kernel.org To: "Martin K. Petersen" Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org On Sat, Jun 07, 2008 at 12:55:38AM -0400, Martin K. Petersen wrote: > +5.1 NORMAL FILESYSTEM > + > + The normal filesystem is unaware that the underlying block device > + is capable of sending/receiving integrity metadata. The IMD will > + be automatically generated by the block layer at submit_bio() time > + in case of a WRITE. A READ request will cause the I/O integrity > + to be verified upon completion. > + > + IMD generation and verification can be toggled using the > + > + /sys/class/block//integrity/write_generate > + > + and > + > + /sys/class/block//integrity/read_verify > + > + flags. > + All of the sysfs interfaces should be documented in Documentation/ABI/ not here, otherwise they will be tough to find and figure out how to use :) thanks, greg k-h