Re: 2.4.20pre5aa2

[Samuel Flory <sflory@xxxxxxxxxxxx>]

Andi Kleen wrote:

> 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 ? 
 I did not use any special options on the filesystem that had the issue.