From: "Martin K. Petersen" <mkp@mkp.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: status of block-integrity
Date: Mon, 23 Dec 2013 08:35:22 -0500 [thread overview]
Message-ID: <yq11u134rmt.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <20131222192128.GA28532@infradead.org> (Christoph Hellwig's message of "Sun, 22 Dec 2013 11:21:29 -0800")
>>>>> "Christoph" == Christoph Hellwig <hch@infradead.org> writes:
Christoph> We have the block integrity code to support DIF/DIX in the
Christoph> the tree for about 5 and a half years, and we still don't
Christoph> have a single consumer of it.
What do you mean? If you have a DIX-capable HBA (lpfc, qla2xxx, zfcp)
then integrity protection is active from the block layer down. The only
code that's not currently being exercised are the tag interleaving
functions. I was hoping the FS people would use them for back pointers
but nobody seemed to bite.
Christoph> Given that we'll have a lot of work to do in this area with
Christoph> block multiqueue I think it's time to either kill it off for
Christoph> good or make sure we can actually use and test it.
I don't understand why multiqueue would require a lot of work? It's just
an extra scatterlist per request.
And obviously, if there's anything that needs to be done in this area
I'll be happy to do so...
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2013-12-23 14:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-22 19:21 Christoph Hellwig
2013-12-22 20:45 ` Nicholas A. Bellinger
2013-12-23 13:35 ` Martin K. Petersen [this message]
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 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
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 21:43 ` Martin K. Petersen
2014-01-08 7:14 ` Hannes Reinecke
2014-01-08 15:23 ` Martin K. Petersen
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=yq11u134rmt.fsf@sermon.lab.mkp.net \
--to=mkp@mkp.net \
--cc=axboe@kernel.dk \
--cc=hch@infradead.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
Powered by JetHome