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 X-Spam-Level: X-Spam-Status: No, score=-11.9 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,NICE_REPLY_A, SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3C565C4338F for ; Mon, 16 Aug 2021 07:43:42 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 25A8161AED for ; Mon, 16 Aug 2021 07:43:42 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234448AbhHPHoL (ORCPT ); Mon, 16 Aug 2021 03:44:11 -0400 Received: from mail.kernel.org ([198.145.29.99]:47060 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234168AbhHPHoK (ORCPT ); Mon, 16 Aug 2021 03:44:10 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id BA1C761ACF; Mon, 16 Aug 2021 07:43:38 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1629099819; bh=U/7WQDfo/Qzy9+DjcIIAqHhrpYiE7FohGVxSzIJvDVo=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=h8CnmTOXZnIpGStqbefpN8NqUfXS02jg7aHR4K+eppyHbzr+9JN/t2BYf/EykzQQe zvQr0wbG/MTqFl3mXTzk5Z4ofW7x010aZFcYRoOfJvWWztgAm6e5Z2gAhoDOInhA/6 8SF6A9eA5QMGMs3QBPWL+MeRocZu4bX6UOR62fx/EUK/zvEa/MiXHa0rL3xUPzM+Nm o4419Beq4E4sVz7YDZ0CpAE4o0Y/OaD3Ij0Yf7ByapyFK3KkjjTFZDcST9skepALrR yc1T3dhg8CMVanxf/smyUOMzTMvD77u40/gK8mCQBKf7w64AfOwDT/0KsgwoFzHrLK 2KP3sM1FUyK+g== Subject: Re: [f2fs-dev] [PATCH v2] f2fs: introduce blk_alloc_mode mount option To: Daeho Jeong Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com, Daeho Jeong References: <20210809185449.2565768-1-daeho43@gmail.com> <425daf77-8020-26ce-dc9f-019d9a881b78@kernel.org> <071534dd-cf10-38d3-b83b-c833f9c0a70a@kernel.org> From: Chao Yu Message-ID: <50bfbeee-e165-5bcf-1c47-a45ef8b36ebf@kernel.org> Date: Mon, 16 Aug 2021 15:43:36 +0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2021/8/16 15:11, Daeho Jeong wrote: > I agree with you. But still I think "fragment" mode should work even > in low free space conditions. > Otherwise, it will be seeking the free blocks again and again like a busy loop. > Or we can change the block allocation way into adaptive mode under low > free space even staying in "fragment" mode. I think fallbacking to adaptive mode sounds good to me, so the condition of fallback may be there is no more free segments? Thanks, > > If we can handle this, we might use "fragment" mode for both > simulating after fragmentation and making the filesystem fragmented. >