xfs
[Top] [All Lists]

Re: 2.4.20pre5aa2

To: Stephen Lord <lord@xxxxxxx>
Subject: Re: 2.4.20pre5aa2
From: Andi Kleen <ak@xxxxxxx>
Date: Sun, 15 Sep 2002 13:13:24 +0200
Cc: Andrea Arcangeli <andrea@xxxxxxx>, Samuel Flory <sflory@xxxxxxxxxxxx>, Austin Gonyou <austin@xxxxxxxxxxxxxxx>, Christian Guggenberger <christian.guggenberger@xxxxxxxxxxxxxxxxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
In-reply-to: <1032014367.1050.2.camel@xxxxxxxxxxxxxxxxxxxxxxx>
References: <20020911184111.GY17868@xxxxxxxxxxxxxxxxx> <3D81235B.6080809@xxxxxxxxxxxx> <20020913002316.GG11605@xxxxxxxxxxxxxxxxx> <1031878070.1236.29.camel@snafu> <20020913005440.GJ11605@xxxxxxxxxxxxxxxxx> <3D8149F6.9060702@xxxxxxxxxxxx> <20020913125345.GO11605@xxxxxxxxxxxxxxxxx> <3D825422.8000007@xxxxxxxxxxxx> <20020913211844.GP11605@xxxxxxxxxxxxxxxxx> <1032014367.1050.2.camel@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.3.22.1i
On Sat, Sep 14, 2002 at 09:39:24AM -0500, Steve Lord wrote:
> On Fri, 2002-09-13 at 16:18, Andrea Arcangeli wrote:
> 
> > So, returning to xfs, it is possible dbench really generates lots of
> > simultaneous vmaps because of its concurrency, so I would suggest to add
> > an atomic counter increased at every vmap/vmalloc and decreased at every
> > vfree and to check it after every increase storing the max value in a
> > sysctl, to see what's the max concurrency you reach with the vmaps. (you
> > can also export the counter via the sysctl, to verify for no memleaks
> > after unmounting xfs)
> > 
> > Andrea
> 
> There are no vmaps during normal operation on xfs unless you are
> setting extended attributes of more than 4K in size, or you
> used some more obscure mkfs options. Only filesystem recovery will
> use it otherwise. 

Perhaps the original poster used those obscure mkfs options? What option
will trigger huge allocations ? 


-Andi


<Prev in Thread] Current Thread [Next in Thread>