From: "Mingming.cao" <cmm@us.ibm.com>
To: Zhi Yong Wu <zwu.kernel@gmail.com>
Cc: linux-fsdevel@vger.kernel.org, linuxram@linux.vnet.ibm.com,
	Dave Chinner <david@fromorbit.com>,
	Ben Chociej <bchociej@gmail.com>,
	James Northrup <northrup.james@gmail.com>
Subject: Re: VFS hot tracking: How to calculate data temperature?
Date: Fri, 02 Nov 2012 14:27:02 -0700	[thread overview]
Message-ID: <1351891622.23963.4.camel@oc2046235844.ibm.com> (raw)
In-Reply-To: <CAEH94LgUcAL6RquMZKTrDg87_0J2sEqTsDXUbnhrQ37KuMJ4sg@mail.gmail.com>
On Fri, 2012-11-02 at 14:38 +0800, Zhi Yong Wu wrote:
> Here also has another question.
> 
> How to save the file temperature among the umount to be able to
> preserve the file tempreture after reboot?
> 
> This above is the requirement from DB product.
> I thought that we can save file temperature in its inode struct, that
> is, add one new field in struct inode, then this info will be written
> to disk with inode.
> 
> Any comments or ideas are appreciated, thanks.
> 
> 
Maybe could save the last file temperature with extended attributes.
Just save the per-inode temperature only for now.
Mingming
> On Fri, Nov 2, 2012 at 12:04 PM, Zhi Yong Wu <zwu.kernel@gmail.com> wrote:
> > HI, guys
> >
> >    VFS hot tracking currently show result as below, and it is very
> > strange and not nice.
> >
> > inode #279, reads 0, writes 1, avg read time 18446744073709551615,
> > avg write time 5251566408153596, temp 109
> >
> > Do anyone know if there is one simpler but effective way to calculate
> > data temperature?
> >
> > --
> > Regards,
> >
> > Zhi Yong Wu
> 
> 
> 
next prev parent reply	other threads:[~2012-11-02 21:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-02  4:04 VFS hot tracking: How to calculate data temperature? Zhi Yong Wu
2012-11-02  4:43 ` Ram Pai
2012-11-02  6:39   ` Zhi Yong Wu
2012-11-02  6:38 ` Zhi Yong Wu
2012-11-02  8:41   ` Zheng Liu
2012-11-02 20:10     ` Darrick J. Wong
2012-11-05  2:34       ` Zhi Yong Wu
2012-11-05  8:35       ` Dave Chinner
2012-11-05  2:29     ` Zhi Yong Wu
2012-11-06  8:39       ` Zheng Liu
2012-11-06  9:00         ` Zhi Yong Wu
2012-11-07  6:45           ` Zheng Liu
2012-11-06  9:36     ` Ram Pai
2012-11-06 23:10       ` Darrick J. Wong
2012-11-07  6:36         ` Zheng Liu
2012-11-07 19:25           ` Darrick J. Wong
2012-11-08  2:48             ` Zheng Liu
2012-11-02 21:27   ` Mingming.cao [this message]
2012-11-05  2:35     ` Zhi Yong Wu
2012-11-05  8:28       ` Dave Chinner
2012-11-05  8:44         ` Zhi Yong Wu
2012-11-05 10:33           ` Steven Whitehouse
2012-11-05 11:46             ` Zhi Yong Wu
2012-11-05 11:57               ` Steven Whitehouse
2012-11-05 12:18                 ` Zhi Yong Wu
2012-11-05 12:25                   ` Steven Whitehouse
2012-11-09  1:12 ` Zhi Yong Wu
2012-11-09  3:20   ` Zheng Liu
     [not found]   ` <CAPkEcwg0ZHjV3JVxoKSzFqKLHavhGdTufLZBdBGQ6xXDMrSU-w@mail.gmail.com>
2012-11-11 23:32     ` Zhi Yong Wu
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=1351891622.23963.4.camel@oc2046235844.ibm.com \
    --to=cmm@us.ibm.com \
    --cc=bchociej@gmail.com \
    --cc=david@fromorbit.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linuxram@linux.vnet.ibm.com \
    --cc=northrup.james@gmail.com \
    --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).