From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Hyunchul Lee <hyc.lee@gmail.com>, Chao Yu <yuchao0@huawei.com>,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
kernel-team@lge.com, Hyunchul Lee <cheol.lee@lge.com>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] apply write hints to select the type of segments
Date: Fri, 17 Nov 2017 10:36:54 -0800 [thread overview]
Message-ID: <20171117183654.GA77642@jaegeuk-macbookpro.roam.corp.google.com> (raw)
In-Reply-To: <20171117172349.GA22843@infradead.org>
On 11/17, Christoph Hellwig wrote:
>
> Next time please coordinate this with the block list and Jens, who
> actually wrote the patch.
Got it.
>
> > hints segment type
> > ----- ------------
> > WRITE_LIFE_SHORT CURSEG_COLD_DATA
> > WRITE_LIFE_EXTREME CURSEG_HOT_DATA
> > others CURSEG_WARM_DATA
>
> Normally cold data is data with a long lifetime, and extreme is colder
> than cold, so there seems to be some mismatch here.
It was wrong description and I fixed it which matches to implementation.
The below description was merged:
WRITE_LIFE_SHORT CURSEG_HOT_DATA
WRITE_LIFE_EXTREME CURSEG_COLD_DATA
others CURSEG_WARM_DATA
prev parent reply other threads:[~2017-11-17 18:37 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 5:51 Hyunchul Lee
2017-11-09 5:51 ` [RFC PATHC 1/2] f2fs: apply write hints to select the type of segments for buffered write Hyunchul Lee
2017-11-09 8:21 ` Chao Yu
2017-11-09 18:19 ` Jaegeuk Kim
2017-11-09 5:51 ` [RFC PATHC 2/2] f2fs: apply write hints to select the type of segment for direct write Hyunchul Lee
2017-11-11 0:38 ` [f2fs-dev] " Chao Yu
2017-11-13 0:07 ` Hyunchul Lee
2017-11-13 1:24 ` Chao Yu
2017-11-13 1:48 ` Hyunchul Lee
2017-11-09 9:12 ` [RFC PATCH 0/2] apply write hints to select the type of segments Chao Yu
2017-11-09 18:16 ` Jaegeuk Kim
2017-11-10 2:31 ` Chao Yu
2017-11-10 0:23 ` Hyunchul Lee
2017-11-10 6:42 ` Chao Yu
2017-11-13 0:24 ` Hyunchul Lee
2017-11-13 1:26 ` Chao Yu
2017-11-13 1:35 ` Hyunchul Lee
2017-11-13 1:59 ` Chao Yu
2017-11-13 2:25 ` Hyunchul Lee
2017-11-14 4:20 ` Jaegeuk Kim
2017-11-14 6:22 ` Chao Yu
2017-11-15 16:27 ` Jaegeuk Kim
2017-11-16 0:56 ` Hyunchul Lee
2017-11-16 2:52 ` Chao Yu
2017-11-16 3:58 ` Jaegeuk Kim
2017-11-16 4:35 ` Hyunchul Lee
2017-11-17 18:53 ` Jaegeuk Kim
2017-11-20 2:12 ` Hyunchul Lee
2017-11-17 17:23 ` Christoph Hellwig
2017-11-17 18:36 ` Jaegeuk Kim [this message]
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=20171117183654.GA77642@jaegeuk-macbookpro.roam.corp.google.com \
--to=jaegeuk@kernel.org \
--cc=axboe@kernel.dk \
--cc=cheol.lee@lge.com \
--cc=hch@infradead.org \
--cc=hyc.lee@gmail.com \
--cc=kernel-team@lge.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuchao0@huawei.com \
/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
all inboxes | Powered by JetHome®