Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp5229108ybe; Mon, 9 Sep 2019 23:59:00 -0700 (PDT) X-Google-Smtp-Source: APXvYqxqhB7zgqpZyS4W/8GrkHsq0UUL8zesOt/5ZeKRk5S5WsjLXgQbqhX5oeeHIsyIHIZMZfsx X-Received: by 2002:a17:906:c799:: with SMTP id cw25mr6733405ejb.107.1568098740193; Mon, 09 Sep 2019 23:59:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568098740; cv=none; d=google.com; s=arc-20160816; b=fMZ5l1gXlFnh0qDW0t5g3CxBHu/v9UG3ryefc1XVlI7FclgRmm1iXJXiANr+K7DpnE QaW4x0ZBx0gE+u4IlLk4ZoQfWA3QvL49ENhvLa7qfYqouNIA0Ec5/K4Tu2J3LM9GLO6M mYNiDyVqhzz6GhIH5W1MeIBES5wSSDIwhHZXr1QCnMgJd079IlpTXwXfQPTv6Vclxlkn 69dZD7NWkCgV5CFDari0VS9beJ/9mSH5r27icgIMM7nH4I4j41xlJ1YZcIRhPgLEkmQy 7eYV4QJ9YxcuN2tTXeuQWhgNOb7TPpnJCHn8gVBY8dFe9ggnN23/AbZ3YrXtgLasiL17 jpAg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=ZjWMfnzoaRRm5VHRluZaYNSKOTxdaedCKDR3l2gTWdA=; b=BRgd+2RTaNA8HEwb3mmy+YTCux7Dv2n6bWJv+6c7ga7E8dTFTWxrbqyp3ZwsCnnZcC Wn7wEXLGlM0IkBSEenioTNO97a4oHaCoXcnOi1xIy7EJxpn5hnnoNwTVwiDwj4jvJl38 ig3aq43/SbNyE+6ZXdxOtsspXvDqNjbiAp3M1ILCIgEucoXy1lDWbM86ANbwRdedzx3V /eZAsWwP5RxMh0zIwlQbWfb3BG3Q6bAqbOq2sr+ZjPORaczJ/8fN8GG7FA3/mxT40RM1 drbxulwduQ3rplUJKLWPiVuKmkh3iZtQq7JB2TuytsNZ8KpbQdZLA3MQssIvJUdtUuto S/OA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i34si10415783ede.37.2019.09.09.23.58.36; Mon, 09 Sep 2019 23:59:00 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2404105AbfIILch (ORCPT + 99 others); Mon, 9 Sep 2019 07:32:37 -0400 Received: from szxga04-in.huawei.com ([45.249.212.190]:2178 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S2391070AbfIILch (ORCPT ); Mon, 9 Sep 2019 07:32:37 -0400 Received: from DGGEMS407-HUB.china.huawei.com (unknown [172.30.72.59]) by Forcepoint Email with ESMTP id 7A50E883CF089CC4CB43; Mon, 9 Sep 2019 19:32:35 +0800 (CST) Received: from [10.134.22.195] (10.134.22.195) by smtp.huawei.com (10.3.19.207) with Microsoft SMTP Server (TLS) id 14.3.439.0; Mon, 9 Sep 2019 19:32:34 +0800 Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: do not select same victim right again To: Jaegeuk Kim CC: , References: <20190909012532.20454-1-jaegeuk@kernel.org> <69933b7f-48cc-47f9-ba6f-b5ca8f733cba@huawei.com> <20190909080654.GD21625@jaegeuk-macbookpro.roam.corp.google.com> From: Chao Yu Message-ID: <97237da2-897a-8420-94de-812e94aa751f@huawei.com> Date: Mon, 9 Sep 2019 19:32:07 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20190909080654.GD21625@jaegeuk-macbookpro.roam.corp.google.com> Content-Type: text/plain; charset="windows-1252" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.134.22.195] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019/9/9 16:06, Jaegeuk Kim wrote: > On 09/09, Chao Yu wrote: >> On 2019/9/9 9:25, Jaegeuk Kim wrote: >>> GC must avoid select the same victim again. >> >> Blocks in previous victim will occupy addition free segment, I doubt after this >> change, FGGC may encounter out-of-free space issue more frequently. > > Hmm, actually this change seems wrong by sec_usage_check(). > We may be able to avoid this only in the suspicious loop? > > --- > fs/f2fs/gc.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c > index e88f98ddf396..5877bd729689 100644 > --- a/fs/f2fs/gc.c > +++ b/fs/f2fs/gc.c > @@ -1326,7 +1326,7 @@ int f2fs_gc(struct f2fs_sb_info *sbi, bool sync, > round++; > } > > - if (gc_type == FG_GC) > + if (gc_type == FG_GC && seg_freed) That's original solution Sahitya provided to avoid infinite loop of GC, but I suggest to find the root cause first, then we added .invalid_segmap for that purpose. Thanks, > sbi->cur_victim_sec = NULL_SEGNO; > > if (sync) >