Messages in this thread | | | Date | Wed, 29 May 2013 22:37:00 +0200 | From | Andi Kleen <> | Subject | Re: [PATCH 0/3 v3] dcache: make it more scalable on large system |
| |
> As Dave said before, is the last path component sufficient? Or how > about an inode number?
Neither works, the profiler needs to find the file and read it.
inode searching would be incredible expensive, unless the file system provided a "open-by-inode" primitive
In normal operation you only have that event when starting up the program and when each shared library gets mapped in.
-Andi
| |