From: "Eddie Pettis" <pettis.eddie@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: How to locate struct file * from a bio?
Date: Wed, 31 Jan 2007 09:34:54 -0500 [thread overview]
Message-ID: <d66e87630701310634s385db5adwa82e2194188efa81@mail.gmail.com> (raw)
Short question: Is it possible to locate the struct file * associated
with a bio? If so, how?
Longer version: I am working on a project that requires measuring the
popularity of each file in a filesystem. I have made several attempts
to locate all the file reads by grepping for ->readpage() and
->readpages() calls, but I am still missing several file reads. I
have not yet looked for file writes.
I *have* been able to catch every bio access, which leads to my
question. Is it possible to locate the struct file * associated with
a bio? If so, how? Efficiency is not my primary issue right now.
I'm mainly concerned with it "just working."
Thanks in advance!
--
Eddie Pettis
Electrical and Computering Engineering
Purdue University
next reply other threads:[~2007-01-31 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 14:34 Eddie Pettis [this message]
2007-01-31 14:44 ` Al Viro
2007-01-31 14:51 ` Al Viro
2007-01-31 15:18 ` Helge Hafting
2007-01-31 18:45 ` Jan Engelhardt
2007-01-31 18:55 ` Eddie Pettis
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=d66e87630701310634s385db5adwa82e2194188efa81@mail.gmail.com \
--to=pettis.eddie@gmail.com \
--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
all inboxes | Powered by JetHome®