From: mingming cao <mingming@oracle.com>
To: Zhi Yong Wu <zwu.kernel@gmail.com>
Cc: lsf-pc@lists.linux-foundation.org, linux-fsdevel@vger.kernel.org,
chris.mason@fusionio.com, linuxram@linux.vnet.ibm.com
Subject: Re: [LSF/MM TOPIC] VFS hot tracking
Date: Thu, 07 Feb 2013 13:04:15 -0800 [thread overview]
Message-ID: <511416CF.5080600@oracle.com> (raw)
In-Reply-To: <CAEH94Lgfk5C_=Ni2tHsUBuiKC1fxPdQFmdiprgsV1Vh2TVZ3ZA@mail.gmail.com>
On 02/07/2013 08:24 AM, Zhi Yong Wu wrote:
> HI,
>
> If some guy is interested in this topic, i would like to talk about
> VFS hot tracking.
>
> The feature will add the support for tracking data temperature
> information in VFS layer. Essentially, this means maintaining some key
> hot data statistics (like number of reads/writes, last read/write
> time, frequency of reads/writes), then distilling those numbers down
> to a single "temperature" value that reflects what data is "hot", then
> specific FS such as btrfs will take use of the temperature infomation
> to move hot data to SSDs, or do the defragmetation.
>
> In this talk, i would discuss its current implementation and how
> its key points are resolved such as memory consumption, how its hot
> data is updated periodically, etc.
>
> If you have any suggestions, pleas let me know, thanks.
>
>
That sounds a good fit for the LSF discussion. I am happy to hear the
update of this feature and where it will go from here. Especially
discussions of APIs that expose the data hotness and how that
information could be used by filesystems and storages.
Mingming
next prev parent reply other threads:[~2013-02-07 21:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 16:24 [LSF/MM TOPIC] VFS hot tracking Zhi Yong Wu
2013-02-07 21:04 ` mingming cao [this message]
2013-02-07 23:48 ` james northrup
2013-02-08 0:55 ` Zhi Yong Wu
2013-02-08 5:38 ` Zheng Liu
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=511416CF.5080600@oracle.com \
--to=mingming@oracle.com \
--cc=chris.mason@fusionio.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linuxram@linux.vnet.ibm.com \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=zwu.kernel@gmail.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).