linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhi Yong Wu <zwu.kernel@gmail.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>,
	linux-kernel mlist <linux-kernel@vger.kernel.org>
Subject: Re: VFS hot tracking: How to calculate data temperature?
Date: Tue, 6 Nov 2012 17:00:19 +0800	[thread overview]
Message-ID: <CAEH94Li_9VfDKoFDjxZv3cjs3wn2p_dfJmnCyRbynku6EDSeHQ@mail.gmail.com> (raw)
In-Reply-To: <20121106083918.GA6090@gmail.com>

On Tue, Nov 6, 2012 at 4:39 PM, Zheng Liu <gnehzuil.liu@gmail.com> wrote:
> On Mon, Nov 05, 2012 at 10:29:39AM +0800, Zhi Yong Wu wrote:
>> On Fri, Nov 2, 2012 at 4:41 PM, Zheng Liu <gnehzuil.liu@gmail.com> 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.
>> Great idea,  temperature saving function is maybe very specific to FS.
>> But i am wondering if we can find one generic way to save temperature
>> info at first.
>
> I don't think a generic way is better because it cannot support a
> variety of filesystems.  So maybe you must answer this question firstly:
> how many filesystems do you want to save this info? such as ext4, xfs,
> btrfs, etc.  Then we can try to find a generic way.  If only these three
> filesystems you want to support, maybe saving in xattr is an optional
> way.
yes, xattr is one good choice from currect discussion result. Maybe we
can provide one generic way, and one callback registering
infrastructure, if FS register its own saving callback, this callback
function will be used, otherwise the generic way will be applied.

By the way, as what Dave mentioned, the patchset v4+ review has
highest priority, then the way how to calc data temperature, and the
lowest priority is the way how to save data temperature info.

>
> Regards,
> Zheng



-- 
Regards,

Zhi Yong Wu

  reply	other threads:[~2012-11-06  9:00 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 [this message]
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=CAEH94Li_9VfDKoFDjxZv3cjs3wn2p_dfJmnCyRbynku6EDSeHQ@mail.gmail.com \
    --to=zwu.kernel@gmail.com \
    --cc=bchociej@gmail.com \
    --cc=cmm@us.ibm.com \
    --cc=david@fromorbit.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxram@linux.vnet.ibm.com \
    --cc=northrup.james@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).