[Top] [All Lists]

Re: [PATCH] Tweak tracing allocation sizes

To: Lachlan McIlroy <lachlan@xxxxxxx>, xfs-dev <xfs-dev@xxxxxxx>, xfs-oss <xfs@xxxxxxxxxxx>
Subject: Re: [PATCH] Tweak tracing allocation sizes
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 2 Sep 2008 17:54:01 -0400
In-reply-to: <20080902062722.GF15962@disturbed>
References: <48BCD3BE.5040107@xxxxxxx> <20080902055604.GD15962@disturbed> <48BCD93E.9040407@xxxxxxx> <20080902062722.GF15962@disturbed>
User-agent: Mutt/1.5.18 (2008-05-17)
On Tue, Sep 02, 2008 at 04:27:22PM +1000, Dave Chinner wrote:
> > - maybe a very large global trace buffer that is allocated at mount
> > time and shared by all inodes?
> Sure, we've got that for various other trace types (e.g. the "vnode"
> trace). You'd need to add idbg stuff for filtering based on the
> inode the buffer belongs to....

That's probably the best idea.  Currently all these per-object ktrace
buffers do really large no-MAYFAIL allocation all over.  They are in
fact the remaining reason not to simply directly call vmalloc for
large allocations instead of all our current mess in the kmem_

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