From: Hannes Reinecke <hare@suse.de>
To: Christoph Hellwig <hch@infradead.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: status of block-integrity
Date: Fri, 03 Jan 2014 16:01:47 +0100 [thread overview]
Message-ID: <52C6D0DB.1050906@suse.de> (raw)
In-Reply-To: <20131222192128.GA28532@infradead.org>
On 12/22/2013 08:21 PM, Christoph Hellwig wrote:
> We have the block integrity code to support DIF/DIX in the the tree for
> about 5 and a half years, and we still don't have a single consumer of
> it. By normal kernel rules it should never have been merged, or at
> least the bitrot long removed.
>
> Given that we'll have a lot of work to do in this area with block
> multiqueue I think it's time to either kill it off for good or make sure
> we can actually use and test it.
Which would make an ideal topic for LSF, wouldn't it?
Personally, I doubt it's a good idea to kill it off, but
a proper (userland) API for it has been a long time missing.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2014-01-03 15:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-22 19:21 status of block-integrity Christoph Hellwig
2013-12-22 20:45 ` Nicholas A. Bellinger
2013-12-23 13:35 ` Martin K. Petersen
2013-12-23 13:48 ` Christoph Hellwig
2013-12-31 19:41 ` berthiaume, wayne
2014-01-07 8:28 ` Ric Wheeler
2014-01-07 13:33 ` Hannes Reinecke
2014-01-07 13:33 ` Hannes Reinecke
2014-01-07 23:34 ` Matthew Wilcox
2014-01-08 0:05 ` James Bottomley
2014-01-08 15:43 ` Martin K. Petersen
2014-01-03 15:01 ` Hannes Reinecke [this message]
2014-01-03 20:03 ` Martin K. Petersen
2014-01-07 1:36 ` Darrick J. Wong
2014-01-07 7:17 ` Hannes Reinecke
2014-01-07 7:17 ` Hannes Reinecke
2014-01-07 21:43 ` Martin K. Petersen
2014-01-08 7:14 ` Hannes Reinecke
2014-01-08 7:14 ` Hannes Reinecke
2014-01-08 15:23 ` Martin K. Petersen
2014-01-09 11:19 ` Hannes Reinecke
2014-01-09 11:19 ` Hannes Reinecke
2014-01-10 1:49 ` Martin K. Petersen
2014-01-07 15:06 ` Chuck Lever
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=52C6D0DB.1050906@suse.de \
--to=hare@suse.de \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.