Return-Path: Received: from aserp1040.oracle.com ([141.146.126.69]:51955 "EHLO aserp1040.oracle.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751448AbcCFNDb (ORCPT ); Sun, 6 Mar 2016 08:03:31 -0500 To: Andreas Dilger Cc: Jens Axboe , linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org, calvinowens@fb.com, hch@lst.de Subject: Re: [PATCH 0/11] Update version of write stream ID patchset From: "Martin K. Petersen" References: <1457107853-8689-1-git-send-email-axboe@fb.com> <56AF7A2D-DF4F-4973-B4F6-6F515A8C500C@dilger.ca> Date: Sun, 06 Mar 2016 08:03:18 -0500 In-Reply-To: <56AF7A2D-DF4F-4973-B4F6-6F515A8C500C@dilger.ca> (Andreas Dilger's message of "Sat, 5 Mar 2016 23:13:22 -0700") Message-ID: MIME-Version: 1.0 Content-Type: text/plain Sender: linux-fsdevel-owner@vger.kernel.org List-ID: >>>>> "Andreas" == Andreas Dilger writes: Andreas, Andreas> What are your thoughts on reserving a small number of the Andreas> stream ID values for filesystem metadata (e.g. the first 31 Andreas> since 0 == unused)? The stream ID address space might be 16-bit but the devices currently being discussed can only handle a few concurrently open streams (4, 8, 16). Discussions are ongoing about whether the devices should be able to implicitly close a stream based on LRU or something similar when the hw max is reached. But as it stands you have to explicitly close an existing stream with a separate command when the max is reached. Otherwise a write with a previously unused stream ID will fail. I.e. there is a significant cost to switching between stream IDs and thus I am afraid the current stuff isn't well suited to having a fine grained tagging approach like the one you are proposing. -- Martin K. Petersen Oracle Linux Engineering