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 8D57FE7D0A7 for ; Thu, 21 Sep 2023 20:23:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231796AbjIUUXH (ORCPT ); Thu, 21 Sep 2023 16:23:07 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49424 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231654AbjIUUWn (ORCPT ); Thu, 21 Sep 2023 16:22:43 -0400 Received: from mail-oi1-f176.google.com (mail-oi1-f176.google.com [209.85.167.176]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D29674B70A; Thu, 21 Sep 2023 10:24:52 -0700 (PDT) Received: by mail-oi1-f176.google.com with SMTP id 5614622812f47-3aa14ed0e7eso652882b6e.1; Thu, 21 Sep 2023 10:24:52 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695317091; x=1695921891; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=rshe0jW7UhxhoxHzQRdwHHly+hnX6L1+KyeP6WuSdms=; b=Z+IW+nx4wDQcTjHdy9q4ktNMuEQQ7Qr2EFvRMUsGU7VGjjsjwTACQB+QNOLqITHa5w hqspMx5KpRPSDGcgsJ13heS/ch/kJItAJVOfy5HrDzNwyQMmIgSpP/MJpUd+FHEsa1Ut 9BFsxjsgk45bIWWeQhP27RNsZbQt7yRVK8nUxi5AMEA+KkrH+65umSKgWpimdRuj+UB+ VHA0SsFtQxsOzkaszJVEir8rSGUgqLweuHsc/6rCn28F3gapaOrhxvQLfOK0RzmuS44H 8yDb0nkYUToJaLoI2ofxe8Zn0OE2gyduehAlnIoMHKvV9qCUCTGTHp4OlmCXrvJbkxiz 4wSg== X-Gm-Message-State: AOJu0YzOFewXulSn5NUOBRJGvHPPbhKVEHoSMbSIsrBjExl5cVZzWcZ5 bQzDQ4V63QhThDTI120N35YOWDY9Mc8= X-Google-Smtp-Source: AGHT+IEckYqWZk5F9LFw20ucVdeJ8Lr3aC+IsVyPzXDqHASE0LSTBOEzKe0qNxhV6kLLw7xkoMLFug== X-Received: by 2002:a05:6a20:3c8a:b0:158:143d:e215 with SMTP id b10-20020a056a203c8a00b00158143de215mr12630984pzj.1.1695306430192; Thu, 21 Sep 2023 07:27:10 -0700 (PDT) Received: from ?IPV6:2620:15c:211:201:6903:9a1f:51f3:593e? ([2620:15c:211:201:6903:9a1f:51f3:593e]) by smtp.gmail.com with ESMTPSA id y7-20020a637d07000000b0054fa8539681sm1362140pgc.34.2023.09.21.07.27.08 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 21 Sep 2023 07:27:09 -0700 (PDT) Message-ID: <8781636a-57ac-4dbd-8ec6-b49c10c81345@acm.org> Date: Thu, 21 Sep 2023 07:27:08 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 00/13] Pass data temperature information to zoned UFS devices Content-Language: en-US To: Niklas Cassel Cc: Matthew Wilcox , Jens Axboe , "linux-block@vger.kernel.org" , "linux-scsi@vger.kernel.org" , "linux-fsdevel@vger.kernel.org" , "Martin K . Petersen" , Christoph Hellwig References: <20230920191442.3701673-1-bvanassche@acm.org> <1522d8ec-6b15-45d5-b6d9-517337e2c8cf@acm.org> From: Bart Van Assche In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-fsdevel@vger.kernel.org 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." I do not want to reopen the discussion about NVMe streams. Thanks, Bart.