From: Daeho Jeong <daeho43@gmail.com>
To: Chao Yu <chao@kernel.org>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com,
Daeho Jeong <daehojeong@google.com>
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: <CACOAw_x1F6Uu3p9RA8S7XBXnEYsnjPFY0JSG_VqBLrUjqAGeCA@mail.gmail.com> (raw)
In-Reply-To: <dc21e445-126d-ef74-3d09-c5a71782ed2a@kernel.org>
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.
WARNING: multiple messages have this Message-ID (diff)
From: Daeho Jeong <daeho43@gmail.com>
To: Chao Yu <chao@kernel.org>
Cc: Daeho Jeong <daehojeong@google.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
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: <CACOAw_x1F6Uu3p9RA8S7XBXnEYsnjPFY0JSG_VqBLrUjqAGeCA@mail.gmail.com> (raw)
In-Reply-To: <dc21e445-126d-ef74-3d09-c5a71782ed2a@kernel.org>
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.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2021-08-16 7:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 18:54 [PATCH v2] f2fs: introduce blk_alloc_mode mount option Daeho Jeong
2021-08-09 18:54 ` [f2fs-dev] " Daeho Jeong
2021-08-11 1:58 ` Chao Yu
2021-08-11 1:58 ` Chao Yu
2021-08-11 5:41 ` Daeho Jeong
2021-08-11 5:41 ` Daeho Jeong
2021-08-11 12:41 ` Chao Yu
2021-08-11 12:41 ` Chao Yu
2021-08-16 4:57 ` Daeho Jeong
2021-08-16 4:57 ` Daeho Jeong
2021-08-16 6:28 ` Chao Yu
2021-08-16 6:28 ` Chao Yu
2021-08-16 7:11 ` Daeho Jeong [this message]
2021-08-16 7:11 ` Daeho Jeong
2021-08-16 7:43 ` Chao Yu
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACOAw_x1F6Uu3p9RA8S7XBXnEYsnjPFY0JSG_VqBLrUjqAGeCA@mail.gmail.com \
--to=daeho43@gmail.com \
--cc=chao@kernel.org \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.