On Thu, May 21, 2009 at 02:09:42PM -0600, Matthew Wilcox wrote:
> On Thu, May 21, 2009 at 04:01:03PM -0400, Theodore Ts'o wrote:
> > This is not intended for merging; but it's useful for determining how
> > much varous fields in the struct inode space, and whether there is any
> > padding leading to waste, especially on a 64-bit platforms.
>
> Why not just use acme's pahole?
>
Because I didn't know about it, and now that I've looked at it, it
requires compiling the kernel with CONFIG_DEBUG_INFO, which means the
kernel takes a lot longer to build. What I did is a bit more hackish,
to be sure, but it's faster to drop it into the tree and then run it
under kvm and then pull it out of the console logs. If you were
planning on investigating a large number of structures, acme's
solution probably is a better one; but if you only need one, it might
be faster to whip up a custom kernel module, perhaps built out of the
tree, instead of rebuilding the entire kernel with CONFIG_DEBUG_INFO.
- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
