From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Can Sar <csar@stanford.edu>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Page/Buffer Cache: Traversing Dirty Buffers
Date: Mon, 11 Oct 2004 08:39:42 -0300 [thread overview]
Message-ID: <20041011113942.GC417@logos.cnet> (raw)
In-Reply-To: <C6322819-1B77-11D9-8CAE-000393B3D4EC@stanford.edu>
On Mon, Oct 11, 2004 at 04:22:02AM -0700, Can Sar wrote:
> Hi,
>
> I know this is not really the right place for asking general questions,
> but I have read the source and searched the web and LKML archives for 2
> days without much avail.
> I am writing a driver for a research project, and need to be able to
> traverse all dirty buffers in the buffer cache, for this device. I have
> read through buffer.c and several other files a dozen times, but have
> not been able to pin down exactly how to get access to the buffer
> cache. If someone could point any files that I should look at, to get a
> pointer to all the dirty buffers associated with a device, I would be
> very happy.
>
> Thank you very much for your help,
> Can Sar
What kernel version are you using?
Look at fs/buffer.c sync_buffers() & related functions.
prev parent reply other threads:[~2004-10-12 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-11 11:22 Page/Buffer Cache: Traversing Dirty Buffers Can Sar
2004-10-11 11:39 ` Marcelo Tosatti [this message]
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=20041011113942.GC417@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=csar@stanford.edu \
--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