From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Zhi Yong Wu <zwu.kernel@gmail.com>,
linux-fsdevel@vger.kernel.org, linuxram@linux.vnet.ibm.com,
Dave Chinner <david@fromorbit.com>,
cmm@us.ibm.com, Ben Chociej <bchociej@gmail.com>,
James Northrup <northrup.james@gmail.com>
Subject: Re: VFS hot tracking: How to calculate data temperature?
Date: Fri, 2 Nov 2012 13:10:48 -0700 [thread overview]
Message-ID: <20121102201048.GA20993@blackbox.djwong.org> (raw)
In-Reply-To: <20121102084109.GA19753@gmail.com>
On Fri, Nov 02, 2012 at 04:41:09PM +0800, Zheng Liu wrote:
> On Fri, Nov 02, 2012 at 02:38:29PM +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.
>
> Hi Zhiyong,
>
> I think that we might define a callback function. If a filesystem wants
> to save these data, it can implement a function to save them. The
> filesystem can decide whether adding it or not by themselves.
>
> BTW, actually I don't really care about how to save these data because I
> only want to observe which file is accessed in real time, which is very
> useful for me to track a problem in our product system.
<shrug> I _think_ the vfs quota code simply asks the filesystem for a special
inode where it save the quota data in whatever (FS-agnostic) format it wants.
Have you considered something like that?
(Or, maybe everyone secretly hates doing that? Secret files, yaaay...)
--D
>
> Regards,
> Zheng
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-11-02 20:11 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 [this message]
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
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=20121102201048.GA20993@blackbox.djwong.org \
--to=darrick.wong@oracle.com \
--cc=bchociej@gmail.com \
--cc=cmm@us.ibm.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).