linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Viacheslav Dubeyko <Slava.Dubeyko@ibm.com>
To: "slava@dubeyko.com" <slava@dubeyko.com>,
	"bvanassche@acm.org" <bvanassche@acm.org>,
	"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: Fri, 24 Jan 2025 21:11:10 +0000	[thread overview]
Message-ID: <0fbbd5a488cdbd4e1e1d1d79ea43c39582569f5a.camel@ibm.com> (raw)
In-Reply-To: <39de3063-a1c8-4d59-8819-961e5a10cbb9@acm.org>

Hi Bart,

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.
> 
> Hi Slava,
> 
> 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.

Which existing approaches would you like to compare?
And what could we imply by effectiveness of the approach? Do you have
a vision how we can estimate the effectiveness? :)

Thanks,
Slava.



  reply	other threads:[~2025-01-24 21:11 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 [this message]
2025-01-27 20:37     ` Bart Van Assche
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=0fbbd5a488cdbd4e1e1d1d79ea43c39582569f5a.camel@ibm.com \
    --to=slava.dubeyko@ibm.com \
    --cc=bvanassche@acm.org \
    --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