LKML Archive on
help / color / mirror / Atom feed
From: Daeho Jeong <>
To: Chao Yu <>
	Daeho Jeong <>
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: introduce blk_alloc_mode mount option
Date: Mon, 16 Aug 2021 00:11:14 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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.

If we can handle this, we might use "fragment" mode for both
simulating after fragmentation and making the filesystem fragmented.

  reply	other threads:[~2021-08-16  7:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-09 18:54 Daeho Jeong
2021-08-11  1:58 ` [f2fs-dev] " Chao Yu
2021-08-11  5:41   ` Daeho Jeong
2021-08-11 12:41     ` Chao Yu
2021-08-16  4:57       ` Daeho Jeong
2021-08-16  6:28         ` Chao Yu
2021-08-16  7:11           ` Daeho Jeong [this message]
2021-08-16  7:43             ` Chao Yu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \
    --subject='Re: [f2fs-dev] [PATCH v2] f2fs: introduce blk_alloc_mode mount option' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).