From: Christoph Hellwig <hch@infradead.org>
To: Hyunchul Lee <hyc.lee@gmail.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>, 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 09:23:49 -0800 [thread overview]
Message-ID: <20171117172349.GA22843@infradead.org> (raw)
In-Reply-To: <1510206688-12767-1-git-send-email-hyc.lee@gmail.com>
Next time please coordinate this with the block list and Jens, who
actually wrote the patch.
> 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.
next parent reply other threads:[~2017-11-17 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1510206688-12767-1-git-send-email-hyc.lee@gmail.com>
2017-11-17 17:23 ` Christoph Hellwig [this message]
2017-11-17 18:36 ` [RFC PATCH 0/2] apply write hints to select the type of segments Jaegeuk Kim
[not found] <5A08F6CA.6040507@gmail.com>
[not found] ` <5bd3945c-16f8-a718-a140-44589ceb490a@huawei.com>
[not found] ` <5A090283.60206@gmail.com>
[not found] ` <20171114042024.GA13008@jaegeuk-macbookpro.roam.corp.google.com>
[not found] ` <3dd3f540-f5e5-2d58-99ef-6abf18bad923@huawei.com>
[not found] ` <20171115162730.GC33528@jaegeuk-macbookpro.roam.corp.google.com>
[not found] ` <5A0CE25A.9090506@gmail.com>
[not found] ` <533fb91e-21af-513e-f587-619498b1f848@huawei.com>
[not found] ` <20171116035858.GA73172@jaegeuk-macbookpro.roam.corp.google.com>
[not found] ` <5A0D15A9.3090706@gmail.com>
2017-11-17 18:53 ` Jaegeuk Kim
2017-11-20 2:12 ` Hyunchul Lee
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=20171117172349.GA22843@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=cheol.lee@lge.com \
--cc=hyc.lee@gmail.com \
--cc=jaegeuk@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).