linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [PATCH 1/5] f2fs: add mount option for segment allocation policy
Date: Tue, 27 Feb 2018 18:33:40 +0800	[thread overview]
Message-ID: <3dfa29d2-4a37-f2f2-648d-885dbda1cdf6@huawei.com> (raw)
In-Reply-To: <20180226174731.26679-1-jaegeuk@kernel.org>

Hi Jaegeuk,

On 2018/2/27 1:47, Jaegeuk Kim wrote:
> This patch adds an mount option, "alloc_mode=%s" having two options, "default"
> and "reuse".
> 
> In "alloc_mode=reuse" case, f2fs starts to allocate segments from 0'th segment
> all the time to reassign segments. It'd be useful for small-sized eMMC parts.

We needs to add Doc for this mount option. ;)

Thanks,

  parent reply	other threads:[~2018-02-27 10:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-26 17:47 [PATCH 1/5] f2fs: add mount option for segment allocation policy Jaegeuk Kim
2018-02-26 17:47 ` [PATCH 2/5] f2fs: add auto tuning for small devices Jaegeuk Kim
2018-02-27 10:35   ` Chao Yu
2018-02-26 17:47 ` [PATCH 3/5] f2fs: set readdir_ra by default Jaegeuk Kim
2018-02-27 10:35   ` Chao Yu
2018-02-26 17:47 ` [PATCH 4/5] f2fs: issue discard aggressively in the gc_urgent mode Jaegeuk Kim
2018-02-27 10:36   ` Chao Yu
2018-03-01  2:37   ` Jaegeuk Kim
2018-02-26 17:47 ` [PATCH 5/5] f2fs: don't stop GC if GC is contended Jaegeuk Kim
2018-02-27 10:36   ` Chao Yu
2018-02-27 10:33 ` Chao Yu [this message]
2018-02-28  5:09 ` [PATCH 1/5 v2] f2fs: add mount option for segment allocation policy Jaegeuk Kim
2018-02-28  9:33   ` Chao Yu
2018-02-28 13:47   ` [f2fs-dev] " Chao Yu
2018-03-01  2:53     ` Jaegeuk Kim
2018-02-28 13:52   ` 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=3dfa29d2-4a37-f2f2-648d-885dbda1cdf6@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=jaegeuk@kernel.org \
    --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 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).