On Thu, 12 Jan 2023 22:24:53 +0000 Matthew Wilcox <willy@xxxxxxxxxxxxx> wrote: > > Great! How do I translate this to files? Do I just do a full scan on the > > entire device to find which file maps to an inode? And I'm guessing that > > the ofs is the offset into the file? > > 'ofs' is, yes. That should have been called 'pos'. > > And as you know, inodes can have multiple names in the filesystem. > I imagine you'd want to trace open() to see which names are being > opened; you can fstat the fd to build the ino->name lookup. I'm not sure which file that points to the inode matters. I'm guessing that if I have two files that are hard-linked together, and I run the readahead() system call on one of them, it will speed up a read of the other one. Or am I mistaken? If I'm not mistaken, then just finding any file that is mapped to the inode is sufficient. The purpose of this is to speed up boot by having portions of the files being read already in the page cache when they are needed. -- Steve
