[lkml]   [2004]   [Jan]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Request: I/O request recording
Bart Samwel <> wrote:
> >
> > Linux caches disk data on a per-file basis. So if you preload pagecache
> > via the /dev/hda1 "file", that is of no benefit to the /etc/passwd file.
> > Each one has its own unique pagecache. When reading pages for /etc/passwd
> > we don't go looking for the same disk blocks in the cache of /dev/hda1.
> >
> > Which is why the userspace cache preloading needs to know the pathnames of
> > all the relevant files - it needs to open and read each one, applying
> > knowledge of disk layout while doing it.
> Hmmm, that explains why this didn't work. :( So if I wanted to do this
> completely from user space using only block_dump data I'd probably have
> to go through all files and find out if they had any blocks in common
> with my preload set -- presuming there is a way to find that out, which
> there probably isn't. That makes this idea pretty much useless, I'm
> sorry to have bothered you with it.

You could certainly do that. Given disk block #N you need to search all
files on the disk asking "who owns this block". The FIBMAP ioctl can be
used on most filesystems (ext2, ext3, others..) to find out which blocks a
file is using. See bmap.c in

Unfortunately you cannot determine a directory's blocks in this way.
Ext3's directories live in the /dev/hda1 pagecache anyway. ext2's
directories each have their own pagecache.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:00    [W:0.094 / U:10.744 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site