From: Hannes Reinecke <hare@suse.de>
To: "Darrick J. Wong" <darrick.wong@oracle.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
chuck.lever@oracle.com
Cc: Christoph Hellwig <hch@infradead.org>,
Jens Axboe <axboe@kernel.dk>,
linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: status of block-integrity
Date: Tue, 07 Jan 2014 08:17:47 +0100 [thread overview]
Message-ID: <52CBAA1B.7000509@suse.de> (raw)
In-Reply-To: <20140107013646.GB10297@birch.djwong.org>
On 01/07/2014 02:36 AM, Darrick J. Wong wrote:
> On Fri, Jan 03, 2014 at 03:03:42PM -0500, Martin K. Petersen wrote:
>>>>>>> "Hannes" == Hannes Reinecke <hare@suse.de> writes:
>>
>> Hannes> Personally, I doubt it's a good idea to kill it off, but a
>> Hannes> proper (userland) API for it has been a long time missing.
>>
>> Before we throw the baby out with the bath water, maybe Darrick can fill
>> us in on the progress of the aio passthrough interface?
>
> I haven't made much progress on it -- I haven't seen any earnest demand for it.
>
Of course not. Who should be demanding it? Application developer
tend to code to existing interfaces.
> Last year Chuck Lever said that some NFS working group was looking defining an
> interface it... has there been any progress? It doesn't sound like there has
> been.
>
Well, the point is that without any defined (userland) interface
it's quite hard to pursuade any userland application developer to
use it.
Plus (as hch rightly pointed out) as there is no defined userland
interface the question is why we bother with all the DIX stuff
in the block layer.
DIF support would be perfectly sufficient to cover any connectivity
issues.
And one feels _really_ silly trying to convince customers from the
benefits of DIX they can't even use.
I've tried that several times, and it doesn't get better over time...
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)
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-01-07 7:17 UTC|newest]
Thread overview: 20+ 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 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 [this message]
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=52CBAA1B.7000509@suse.de \
--to=hare@suse.de \
--cc=axboe@kernel.dk \
--cc=chuck.lever@oracle.com \
--cc=darrick.wong@oracle.com \
--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 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).