On Thu, May 30, 2013 at 10:28 AM, Eric Paris <epa...@parisplace.org> wrote:
>
> How do I tell what is taking time inside selinux_inode_permission?
Go to "annotate" (just press 'a' when the function is highlighted),
which will show you the disassembly and the cost of each instruction.
That's when you really want to use "-e cycles:pp" to get the
instruction-level profile right, though. Otherwise the cost will
usually be assigned to the instructions following the expensive one.
And I can tell you that the cost is almost certainly the cache miss on
the inode->i_security accesses. Which was the reason for that second
patch that moved "sid" to the inode->i_sid field and avoided the extra
dereference.
Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
