From: Andrew Morton <akpm@osdl.org>
To: "Diego Calleja García" <aradorlinux@yahoo.es>
Cc: bart@samwel.tk, felix-kernel@fefe.de, linux-kernel@vger.kernel.org
Subject: Re: Request: I/O request recording
Date: Sun, 25 Jan 2004 16:32:05 -0800 [thread overview]
Message-ID: <20040125163205.10a958aa.akpm@osdl.org> (raw)
In-Reply-To: <20040126012356.3a21ae18.aradorlinux@yahoo.es>
Diego Calleja García <aradorlinux@yahoo.es> wrote:
>
> El Sun, 25 Jan 2004 15:38:03 -0800 Andrew Morton <akpm@osdl.org> escribió:
>
> > 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.
>
> It would be possible to "hijack" the syscalls at libc level and look at what
> the program is doing?
That would work. It misses out on pagefaults, which are kind of syscalls
in disguise. So for any files which were mmapped you'd have to either
assume that all of the file's pages are required, or use mincore() to poke
around and find out which pages were really faulted in.
next prev parent reply other threads:[~2004-01-26 0:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-24 18:10 Felix von Leitner
2004-01-24 18:23 ` Valdis.Kletnieks
2004-01-24 18:26 ` Arjan van de Ven
2004-01-24 19:25 ` Ville Herva
2004-01-24 22:43 ` Arjan van de Ven
2004-01-24 20:11 ` Diego Calleja
2004-01-24 21:09 ` Ville Herva
2004-01-24 23:35 ` Andrew Morton
2004-01-24 23:53 ` Davide Libenzi
2004-01-25 0:03 ` Andrew Morton
2004-01-25 0:09 ` Davide Libenzi
2004-01-25 0:04 ` Valdis.Kletnieks
2004-01-25 0:10 ` Davide Libenzi
2004-01-25 12:26 ` Felipe Alfaro Solana
2004-01-25 22:59 ` Bart Samwel
2004-01-25 23:09 ` Andrew Morton
2004-01-25 23:29 ` Bart Samwel
2004-01-25 23:38 ` Andrew Morton
2004-01-26 0:23 ` Diego Calleja García
2004-01-26 0:32 ` Andrew Morton [this message]
2004-01-26 11:50 ` Bart Samwel
2004-01-26 11:57 ` Andrew Morton
2004-01-27 19:13 ` Bart Samwel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040125163205.10a958aa.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=aradorlinux@yahoo.es \
--cc=bart@samwel.tk \
--cc=felix-kernel@fefe.de \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome