From: "Martin Jambor" <jambormartin@gmail.com>
To: "UZAIR LAKHANI" <uzairr_bs1b@yahoo.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: File System Address Space Operations
Date: Tue, 1 Aug 2006 18:58:46 +0200 [thread overview]
Message-ID: <9615ac9b0608010958u5d25bb47obcfe8f46301c8acc@mail.gmail.com> (raw)
In-Reply-To: <20060801054625.1592.qmail@web37502.mail.mud.yahoo.com>
On 8/1/06, UZAIR LAKHANI <uzairr_bs1b@yahoo.com> wrote:
> Martin Jambor <jambormartin@gmail.com> wrote:
> > On 7/29/06, UZAIR LAKHANI <uzairr_bs1b@yahoo.com>
> > wrote:
> > > Hello All,
> > >
> > > I want to find out the details of the address
> > space
> > > operations. Where can I get the detailed
> > information
> > > about the address space operations.
> >
> > Have a look at
> >
> > a) Documentation/filesystems/vfs.txt
> > b) Documentation/filesystems/Locking and
> > c) some simple fs that uses it (minix?)
>
> Hello All,
>
> Thanks for your reply and help. But the (a) and (b)
> above don't give me enough details about the
> theoretical aspects of address space operations. For
> example why these operations are needed. What is their
> flow etc. If you please give some more links that help
> me understanding address space operations and buffer
> cache issues clearly, then I will be thankful to you.
I think both (a) and (b) are rather good. More stuff I can think about
would include:
* Robert Love: Linux Kernel Development, Chapter 15 (page 269)
* Mel Gorman: Understanding the Linux Virtual Memory Manager,
section 4.4 (available online)
* I guess "Understanding the Linux Kernel" would cover it as well but
I have not had a look at it yet.
* Search Google for "Linux Page Cache." (I, for example, within a few
seconds came across http://www.faqs.org/docs/kernel_2_4/lki-4.html
which does not seem very outdated (at a glance).
I personally learnt about the page cacher by reading the source code
of ramfs and minix, especially the generic kernel handlers of
file_operations and address_space_operations. If you want to really
understand the stuff, you simply have to do it. If you have problems
understanding the code, people at #kernelnewbies
(www.kernelnewbies.org) can and often do help.
HTH
Martin
prev parent reply other threads:[~2006-08-01 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-29 7:15 File System Address Space Operations UZAIR LAKHANI
2006-07-29 16:30 ` Martin Jambor
2006-08-01 5:46 ` UZAIR LAKHANI
2006-08-01 16:56 ` Bryan Henderson
2006-08-01 16:58 ` Martin Jambor [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=9615ac9b0608010958u5d25bb47obcfe8f46301c8acc@mail.gmail.com \
--to=jambormartin@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=uzairr_bs1b@yahoo.com \
/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;
as well as URLs for NNTP newsgroup(s).