From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7510AE7D0A6 for ; Thu, 21 Sep 2023 19:31:26 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231221AbjIUTba (ORCPT ); Thu, 21 Sep 2023 15:31:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43362 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230434AbjIUTak (ORCPT ); Thu, 21 Sep 2023 15:30:40 -0400 Received: from casper.infradead.org (casper.infradead.org [IPv6:2001:8b0:10b:1236::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C9350A241; Thu, 21 Sep 2023 12:27:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=pzyLj/te+pJ0atcMca8/O/Us6PqNEkR5Xz0Y5l8NnVg=; b=piInYrEt+X8wmDUC3mgNPb793R jZ0VFH+yzLf8eaEMHzbrcWvpyVoX40KpY4tRZiidjcjvcObuvInNIAexDPnyjVDhFFlzpA8A8YIbt mUYiA9jkEzEDfLkXLsR22hzdIPxnLWbSY+4D5AYRPtIXaSD9xn3iVahsnbaMfI6k+gGyDQthT1Du2 zwnsTQqjoba0c1BrWlqRknzw9MuTjFciAvP57R25pWEdRcEPZzIFWR5II8DHJK87Xpq904uL/wf8D dSg3g5D+gjNuCP78rFmUe7Exa2TL2oAKTJ0S29NGj/RH5PZ+gGp1Al7zlG6XBRIGrSPlYA5Jkvw2W /EhWfKfw==; Received: from willy by casper.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1qjPKU-00DghM-7I; Thu, 21 Sep 2023 19:27:14 +0000 Date: Thu, 21 Sep 2023 20:27:14 +0100 From: Matthew Wilcox To: Bart Van Assche Cc: Niklas Cassel , Jens Axboe , "linux-block@vger.kernel.org" , "linux-scsi@vger.kernel.org" , "linux-fsdevel@vger.kernel.org" , "Martin K . Petersen" , Christoph Hellwig Subject: Re: [PATCH 00/13] Pass data temperature information to zoned UFS devices Message-ID: References: <20230920191442.3701673-1-bvanassche@acm.org> <1522d8ec-6b15-45d5-b6d9-517337e2c8cf@acm.org> <8781636a-57ac-4dbd-8ec6-b49c10c81345@acm.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8781636a-57ac-4dbd-8ec6-b49c10c81345@acm.org> Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org On Thu, Sep 21, 2023 at 07:27:08AM -0700, Bart Van Assche wrote: > On 9/21/23 00:46, Niklas Cassel wrote: > > Considering that this API (F_GET_FILE_RW_HINT / F_SET_FILE_RW_HINT) was > > previously only used by NVMe (NVMe streams). > > That doesn't sound correct to me. I think support for this API was added > in F2FS in November 2017 (commit 4f0a03d34dd4 ("f2fs: apply write hints > to select the type of segments for buffered write")). That was a few > months after NVMe stream support was added (June 2017) by commit > f5d118406247 ("nvme: add support for streams and directives"). > > > Should NVMe streams be brought back? Yes? No? > > From commit 561593a048d7 ("Merge tag 'for-5.18/write-streams-2022-03-18' > of git://git.kernel.dk/linux-block"): "This removes the write streams > support in NVMe. No vendor ever really shipped working support for this, > and they are not interested in supporting it." It sounds like UFS is at the same stage that NVMe got to -- standard exists, no vendor has committed to actually shipping it. Isn't bringing it back a little premature?