From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0b-00082601.pphosted.com ([67.231.153.30]:19679 "EHLO mx0b-00082601.pphosted.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753404AbcCRRhx (ORCPT ); Fri, 18 Mar 2016 13:37:53 -0400 Subject: Re: [PATCH 0/11] Update version of write stream ID patchset To: "Martin K. Petersen" References: <1457107853-8689-1-git-send-email-axboe@fb.com> <56D9F141.9070803@fb.com> <56D9F8E1.2080702@fb.com> <56DF4A8F.8070103@fb.com> <56EB4963.9030704@fb.com> CC: Dan Williams , Jeff Moyer , linux-fsdevel , , , Christoph Hellwig , Andreas Dilger From: Jens Axboe Message-ID: <56EC3CC9.1060404@fb.com> Date: Fri, 18 Mar 2016 10:37:13 -0700 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On 03/17/2016 07:39 PM, Martin K. Petersen wrote: >>>>>> "Jens" == Jens Axboe writes: > > Jens> You are not missing anything, that's exactly how it is intended, > Jens> and that's how the interface is designed as well. If you want to > Jens> tie extra meaning to this for specific drivers or transports, > Jens> that's fine, and there's nothing that prevents that from > Jens> happening. As it stands, and as it is proposed, it's just a write > Jens> tag/stream ID that we can set on a file or inode, and have passed > Jens> to the driver. Nothing more, nothing less. > > Yep. I'm fine with having the option of letting applications request an > ID from the kernel and being able to tag I/Os. But it is also imperative > that we are able to tag all remaining I/Os automatically. Hashing inode > and device/partition is fine, it does not have to be particularly > clever. > > There are several types of non-flash storage in the pipeline that depend > on being able to identify blocks to disjoint LBA ranges as belonging to > the same "file". So as long as we don't go down the 10-channel flash > controller rat hole I'm perfectly happy... So where do we go from here? Seems to me like the core parts we all agree on, what do we do about the user interface? I can split the patchset into 2 so we can get the core bits merged, and start further discussion on the interface part, if we need to. -- Jens Axboe