From: Bart Van Assche <bvanassche@acm.org>
To: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>,
"slava@dubeyko.com" <slava@dubeyko.com>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Greg Farnum <gfarnum@ibm.com>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"javier.gonz@samsung.com" <javier.gonz@samsung.com>
Subject: Re: [LSF/MM/BPF TOPIC] Generalized data temperature estimation framework
Date: Mon, 27 Jan 2025 12:37:21 -0800 [thread overview]
Message-ID: <833b054b-f179-4bc8-912b-dad057d193cd@acm.org> (raw)
In-Reply-To: <0fbbd5a488cdbd4e1e1d1d79ea43c39582569f5a.camel@ibm.com>
On 1/24/25 1:11 PM, Viacheslav Dubeyko wrote:
> On Fri, 2025-01-24 at 12:44 -0800, Bart Van Assche wrote:
>> On 1/23/25 12:33 PM, Viacheslav Dubeyko wrote:
>>> I would like to discuss a generalized data "temperature"
>>> estimation framework.
>>
>> Is data available that shows the effectiveness of this approach and
>> that compares this approach with existing approaches?
>
> Yes, I did the benchmarking. I can see the quantitative estimation of
> files' temperature.
What has been measured in these benchmarks?
> Which existing approaches would you like to compare?
F2FS has a built-in algorithm for assigning data temperatures.
> And what could we imply by effectiveness of the approach? Do you have
> a vision how we can estimate the effectiveness? :)
Isn't the goal of providing data temperature information to the device
to reduce write amplification (W.A.)? I think that W.A. data would be
useful but I'm not sure whether such data is easy to extract from a
storage device.
Thanks,
Bart.
next prev parent reply other threads:[~2025-01-27 20:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 20:33 Viacheslav Dubeyko
2025-01-24 20:44 ` Bart Van Assche
2025-01-24 21:11 ` Viacheslav Dubeyko
2025-01-27 20:37 ` Bart Van Assche [this message]
2025-01-27 23:42 ` Viacheslav Dubeyko
2025-01-28 22:41 ` Bart Van Assche
2025-01-28 22:57 ` Viacheslav Dubeyko
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=833b054b-f179-4bc8-912b-dad057d193cd@acm.org \
--to=bvanassche@acm.org \
--cc=Slava.Dubeyko@ibm.com \
--cc=gfarnum@ibm.com \
--cc=javier.gonz@samsung.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=slava@dubeyko.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