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 E5110C433EF for ; Thu, 10 Mar 2022 19:10:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240343AbiCJTLe (ORCPT ); Thu, 10 Mar 2022 14:11:34 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48894 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S242341AbiCJTLd (ORCPT ); Thu, 10 Mar 2022 14:11:33 -0500 Received: from mail-il1-x12e.google.com (mail-il1-x12e.google.com [IPv6:2607:f8b0:4864:20::12e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 37EB51965E4 for ; Thu, 10 Mar 2022 11:10:30 -0800 (PST) Received: by mail-il1-x12e.google.com with SMTP id l13so4407715iln.13 for ; Thu, 10 Mar 2022 11:10:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20210112.gappssmtp.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=Z2XnAIZo4F9dSg2/HrPYqXkXeLAaoG9uThWsD0uBJlA=; b=Zs/K8Ho3umHLToueBxMUNe97QzEdc/fHEZhQ7JtJWKvwOgjZ11JXrAWoy0GAhtd0zI Ds6PmqoMAoryy9OdN7rCKqG2max0dWACJrmkby+3VU+kNc3YdiHD6MKmOmJIMwD261Ze dL/7enTzi3bbl5vjuQxDFNp5GXWQswLJnMNLb7qYpVP8pKmByGMd5Am5wz28FHIOq+XV o5C2rZRsaiK45ER8KOtnr0QXOt8DHrHvG92aZN2cjSrzOljHkSygMGXA7+ZxntMUjzG+ slLqs+vTgysxjiGW9RnhGNWaCke+QjEcm3wPYCf04fHEuZhflaQSWQmA8WClSMy+EGRI b67w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=Z2XnAIZo4F9dSg2/HrPYqXkXeLAaoG9uThWsD0uBJlA=; b=pmWJXVQ3Cxv6++/iEQMMYQK5j3qnUVGcRvTtChstOPMqcKJSzcKYKJHXEg7NMkl4Ro eFgT6DiW99t1zNkrreVr9BhCV5dCFJxn/zQsW4XVGgxxP7m+caIJFdSLdpQEnO92Ht1i inJ/4Mnna5By276ugu5v0AyNjeKRrV47W8ezPTjt8x98AsMbNgCwFLbDeUpeDZ7IkRZb F9avTjE04u3YXvAHfZqKm2jyJIaMv3RO1UKQXTENkNkwQF3WpNp07D7Pjxop2xEGSjL9 6O9CBnIiIxV943zxgFqnOL3rFCpUzMuBj5v8nWznOhycrTprFd9N75vWj+SNdzm92HBo pROA== X-Gm-Message-State: AOAM533uAyfF1e92T7bpJKvovaVPvSSBzXQsE5dfqDrpdHUvZ5fnAV/h oxFDtUZU5ij0/eDVzhHtXjYRVQ== X-Google-Smtp-Source: ABdhPJwx7bekaEdUtL1Ejn1IAjB6lGjVlrk24NZLRa7bis8QL16ikKs73/7JzgQhljRrnvGpFxNraA== X-Received: by 2002:a05:6e02:1a8e:b0:2c7:6e36:e154 with SMTP id k14-20020a056e021a8e00b002c76e36e154mr1897043ilv.180.1646939429515; Thu, 10 Mar 2022 11:10:29 -0800 (PST) Received: from [192.168.1.172] ([207.135.234.126]) by smtp.gmail.com with ESMTPSA id k1-20020a056e021a8100b002c64cf94399sm3435510ilv.44.2022.03.10.11.10.28 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 10 Mar 2022 11:10:29 -0800 (PST) Message-ID: Date: Thu, 10 Mar 2022 12:10:27 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1 Subject: Re: [EXT] Re: [PATCH 2/2] block: remove the per-bio/request write hint. Content-Language: en-US To: "Luca Porzio (lporzio)" , Manjong Lee , "david@fromorbit.com" Cc: "hch@lst.de" , "kbusch@kernel.org" , "linux-block@vger.kernel.org" , "linux-fsdevel@vger.kernel.org" , "linux-nvme@lists.infradead.org" , "linux-raid@vger.kernel.org" , "sagi@grimberg.me" , "song@kernel.org" , "seunghwan.hyun@samsung.com" , "sookwan7.kim@samsung.com" , "nanich.lee@samsung.com" , "woosung2.lee@samsung.com" , "yt0928.kim@samsung.com" , "junho89.kim@samsung.com" , "jisoo2146.oh@samsung.com" References: <20220306231727.GP3927073@dread.disaster.area> <20220309133119.6915-1-mj0123.lee@samsung.com> From: Jens Axboe In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-raid@vger.kernel.org On 3/10/22 11:50 AM, Luca Porzio (lporzio) wrote: > Micron Confidential > >> >> You do both realize that this is just the file specific hint? Inode based hints >> will still work fine for UFS. >> >> -- >> Jens Axboe > > Jens, > > Thanks for this reply. > > This whole patch series removes support for per-bio write_hint. > Without bio write_hint, F2FS won't be able to cascade Hot/Warm/Cold > information to SCSI / UFS driver. > > This is my current understanding. I might be wrong but I don't think we > Are concerned with inode hint (as well as file hints). But ufs/scsi doesn't use it in mainline, as far as I can tell. So how does that work? -- Jens Axboe