From mboxrd@z Thu Jan  1 00:00:00 1970
From: Zhi Yong Wu <zwu.kernel@gmail.com>
Subject: Re: VFS hot tracking: How to calculate data temperature?
Date: Mon, 12 Nov 2012 07:32:05 +0800
Message-ID: <CAEH94LhgORaxQJymv8M2FYvqtsVaLWmfzyWKRdn7t-4hyAn9HQ@mail.gmail.com>
References: <CAEH94LjTedn0n00ZtqFxBL=kDA3u8G39q+x79-vPoMYvEKW1gw@mail.gmail.com>
	<CAEH94LiB05bck=w=TnDcg02TttPaanzhCtgPW-o8rVO5uBA4iw@mail.gmail.com>
	<CAPkEcwg0ZHjV3JVxoKSzFqKLHavhGdTufLZBdBGQ6xXDMrSU-w@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	linuxram@linux.vnet.ibm.com, Dave Chinner <david@fromorbit.com>,
	cmm@us.ibm.com, Ben Chociej <bchociej@gmail.com>,
	Zheng Liu <wenqing.lz@taobao.com>,
	"Darrick J. Wong" <darrick.wong@oracle.com>,
	Ram Pai <linuxram@us.ibm.com>,
	Steven Whitehouse <swhiteho@redhat.com>
To: james northrup <northrup.james@gmail.com>
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from mail-bk0-f46.google.com ([209.85.214.46]:60622 "EHLO
	mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1750810Ab2KKXcH (ORCPT
	<rfc822;linux-fsdevel@vger.kernel.org>);
	Sun, 11 Nov 2012 18:32:07 -0500
Received: by mail-bk0-f46.google.com with SMTP id jk13so2131195bkc.19
        for <linux-fsdevel@vger.kernel.org>; Sun, 11 Nov 2012 15:32:05 -0800 (PST)
In-Reply-To: <CAPkEcwg0ZHjV3JVxoKSzFqKLHavhGdTufLZBdBGQ6xXDMrSU-w@mail.gmail.com>
Sender: linux-fsdevel-owner@vger.kernel.org
List-ID: <linux-fsdevel.vger.kernel.org>

On Fri, Nov 9, 2012 at 11:05 PM, james northrup
<northrup.james@gmail.com> wrote:
> is 'temp 109' a bucket of inodes or is temp per-inode?
both.

>
>
> On Thu, Nov 8, 2012 at 5:12 PM, Zhi Yong Wu <zwu.kernel@gmail.com> wrote:
>>
>> 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?
>>
>>  inode 279, reads 0, writes 1, temp 109
>>
>>  Since we have got no better way, and avg read/write times are
>> mid-stage value, i want to show it as above format, do you think of
>> it?
>>
>> >
>> > --
>> > Regards,
>> >
>> > Zhi Yong Wu
>>
>>
>>
>> --
>> Regards,
>>
>> Zhi Yong Wu
>
>



-- 
Regards,

Zhi Yong Wu