[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121018042916.GP2739@dastard>
Date: Thu, 18 Oct 2012 15:29:16 +1100
From: Dave Chinner <david@...morbit.com>
To: Zhi Yong Wu <zwu.kernel@...il.com>
Cc: linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org,
linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org,
linuxram@...ux.vnet.ibm.com, viro@...iv.linux.org.uk,
dave@...os.cz, tytso@....edu, cmm@...ibm.com,
Zhi Yong Wu <wuzhy@...ux.vnet.ibm.com>
Subject: Re: [RFC v3 00/13] vfs: hot data tracking
On Wed, Oct 17, 2012 at 04:57:14PM +0800, Zhi Yong Wu wrote:
> On Tue, Oct 16, 2012 at 4:42 AM, Dave Chinner <david@...morbit.com> wrote:
> > On Wed, Oct 10, 2012 at 06:07:22PM +0800, zwu.kernel@...il.com wrote:
> >> From: Zhi Yong Wu <wuzhy@...ux.vnet.ibm.com>
....
> > (*) Tested on an empty 17TB XFS filesystem with:
> >
> > $ sudo mkfs.xfs -f -l size=131072b,sunit=8 /dev/vdc
> > meta-data=/dev/vdc isize=256 agcount=17, agsize=268435455 blks
> > = sectsz=512 attr=2, projid32bit=0
> > data = bsize=4096 blocks=4563402735, imaxpct=5
> > = sunit=0 swidth=0 blks
> > naming =version 2 bsize=4096 ascii-ci=0
> > log =internal log bsize=4096 blocks=131072, version=2
> > = sectsz=512 sunit=1 blks, lazy-count=1
> > realtime =none extsz=4096 blocks=0, rtextents=0
> > $ sudo mount -o logbsize=256k /dev/vdc /mnt/scratch
> > $ sudo chmod 777 /mnt/scratch
> > $ fs_mark -D 10000 -S0 -n 100000 -s 1 -L 63 -d \
> > /mnt/scratch/0 -d /mnt/scratch/1 -d /mnt/scratch/2 -d \
> > /mnt/scratch/3 -d /mnt/scratch/4 -d /mnt/scratch/5 -d \
> > /mnt/scratch/6 -d /mnt/scratch/7
> > .....
> > 0 21600000 1 16679.3 12552262
> > 0 22400000 1 15412.4 12588587
> > 0 23200000 1 16367.6 14199322
> > 0 24000000 1 15680.4 15741205
> > <hangs here w/ OOM>
> ^^^^In this test, i haven't see you enable hot_track function via
> mount, why did it meet OOM?
I copied the wrong mount command. It was definitely enabled.
Cheers,
Dave.
--
Dave Chinner
david@...morbit.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists