Received: by 2002:a05:6a10:a852:0:0:0:0 with SMTP id d18csp1147465pxy; Thu, 6 May 2021 01:16:19 -0700 (PDT) X-Google-Smtp-Source: ABdhPJx9OIH74jSVgQYkN0HUKqEC2hLeL7xAP3TpGz6SuYtKfSgVpSyAiCShXjk9glqh50RVquwK X-Received: by 2002:aa7:c78a:: with SMTP id n10mr3604103eds.239.1620288979374; Thu, 06 May 2021 01:16:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620288979; cv=none; d=google.com; s=arc-20160816; b=HqOsQfjPgU+QzfVChVKqH7Nm0EYFEOmpyXXD4pvLcTwiKdYzECs8wib+NCbIGdVE/D 3mrxJnIwKelSbCa53diTGdhG/3EkZiDxfMf+4LrMQU8Vw6Gi2CC7nIX7J35Tw85DwQ+z kKicMtfDn5mApeX0+2G3AhZ1h58BCsBFnxjNQm4jFn88rs992orOtX+vxrevGioYgA7q 8yxNpiPnTwCmzi4YO7uEwhibjK4acov6lsXdciq0IzRWDevoGYPWnl6GBTbRl3GcLr3B WL94GaYIOmGGpN0S6QworWKSAMqzVeGQceKYzVvQigO5OLQ4ZGTge4oIUs7wwTK/z5aU cr0g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=BBcZ0rslfq6kvOyVxgHQZqMrOkN8ka0jgtEMuaPnXgw=; b=Xzkngf1TT9M/Zz+3iznfcFMTgM8oMGBMvrArMcaff64h+dhIltzE8xSnHgIPGuyvrk t0dx/TXcxJx8xRJom/Ew47JJ4TjaF6H5B40HAjvN0fwHLLr2UT6mOxpM2Z9o5GadJsAl /01FgV2JzlWaf1foItrroMRNO7DSg7TY4JhiBhODjbxEXIvQ8p58x4kuIrujKs4WfjG5 0UjId3ikJJfpZm8f5+Bfjgn8D4KOXjfNAux6heFSDGWh3miS0jYWrBlASfhu3431kffd pXfvQc/pHIhjZGnIr/6zr6on/nVeoCDIux9jwwvDWXWvga9o9QqZ8jm2Y4qSfZHGVmMo XLcg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id n15si468608edy.29.2021.05.06.01.15.56; Thu, 06 May 2021 01:16:19 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231873AbhEFGhT (ORCPT + 99 others); Thu, 6 May 2021 02:37:19 -0400 Received: from szxga05-in.huawei.com ([45.249.212.191]:17470 "EHLO szxga05-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230078AbhEFGhS (ORCPT ); Thu, 6 May 2021 02:37:18 -0400 Received: from DGGEMS411-HUB.china.huawei.com (unknown [172.30.72.60]) by szxga05-in.huawei.com (SkyGuard) with ESMTP id 4FbP130NtvzkWrK; Thu, 6 May 2021 14:33:43 +0800 (CST) Received: from [10.136.110.154] (10.136.110.154) by smtp.huawei.com (10.3.19.211) with Microsoft SMTP Server (TLS) id 14.3.498.0; Thu, 6 May 2021 14:36:13 +0800 Subject: Re: [PATCH] f2fs: set file as cold when file defragmentation To: Jaegeuk Kim CC: , "chao@kernel.org" , "linux-kernel@vger.kernel.org" , "linux-f2fs-devel@lists.sourceforge.net" References: <20210429062005epcms2p352ef77f96ab66cbffe0c0ab6c1b62d8a@epcms2p3> <3a0ab201-9546-d523-abc7-79df5f637f14@huawei.com> From: Chao Yu Message-ID: Date: Thu, 6 May 2021 14:36:12 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.136.110.154] X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2021/5/6 12:46, Jaegeuk Kim wrote: > On 05/06, Chao Yu wrote: >> On 2021/4/29 14:20, Daejun Park wrote: >>> In file defragmentation by ioctl, all data blocks in the file are >>> re-written out-of-place. File defragmentation implies user will not update >>> and mostly read the file. So before the defragmentation, we set file >>> temperature as cold for better block allocation. >> >> I don't think all fragmented files are cold, e.g. db file. > > I have a bit different opinion. I think one example would be users want to > defragment a file, when the they want to get higher read bandwidth for Multimedia file was already defined as cold file now via default extension list? > usually multimedia files. That's likely to be cold files. Moreover, I don't > think they want to defragment db files which will be fragmented soon? I guess like db files have less update but more access? Thanks, > >> >> We have separated interface (via f2fs_xattr_advise_handler, e.g. setfattr -n >> "system.advise" -v value) to indicate this file is a hot/cold file, so my >> suggestion is after file defragmentation, if you think this file is cold, and >> use setxattr() to set it as cold. >> >> Thanks, >> >>> >>> Signed-off-by: Daejun Park >>> --- >>> fs/f2fs/file.c | 3 +++ >>> 1 file changed, 3 insertions(+) >>> >>> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c >>> index d697c8900fa7..dcac965a05fe 100644 >>> --- a/fs/f2fs/file.c >>> +++ b/fs/f2fs/file.c >>> @@ -2669,6 +2669,9 @@ static int f2fs_defragment_range(struct f2fs_sb_info *sbi, >>> map.m_len = pg_end - pg_start; >>> total = 0; >>> + if (!file_is_cold(inode)) >>> + file_set_cold(inode); >>> + >>> while (map.m_lblk < pg_end) { >>> pgoff_t idx; >>> int cnt = 0; >>> > . >