linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kyle Moffett <mrmacman_g4@mac.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Antonio Vargas <windenntw@gmail.com>,
	"Theodore Ts'o" <tytso@mit.edu>,
	John Richard Moser <nigelenki@comcast.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Linux VFS architecture questions
Date: Mon, 23 Jan 2006 12:50:56 -0500	[thread overview]
Message-ID: <A31CA9FF-4B56-483C-8BCC-CECD9B812844@mac.com> (raw)
In-Reply-To: <84144f020601230900x477dd21am8d94f382e37c5072@mail.gmail.com>

On Jan 23, 2006, at 12:00, Pekka Enberg wrote:
> Hi Kyle,
>
> On 1/23/06, Kyle Moffett <mrmacman_g4@mac.com> wrote:
>> Great!  I'm trying to learn about filesystem design and  
>> implementation, which is why I started writing my own hfsplus  
>> filesystem (otherwise I would have just used the in-kernel one).   
>> Do you have any recommended reading (either online or otherwise)  
>> for someone trying to understand the kernel's VFS and blockdev  
>> interfaces?  I _think_ I understand the basics of buffer_head,  
>> super_block, and have some idea of how to use aops, but it's tough  
>> going trying to find out what functions to call to manage cached  
>> disk blocks, or under what conditions the various VFS  functions  
>> are called.  I'm trying to write up a "Linux Disk-Based Filesystem  
>> Developers Guide" based on what I learn, but it's remarkably  
>> sparse so far.
>
> Did you read Documentation/filesystems/vfs.txt?

Yeah, that was the first thing I looked at.  Once I've got things  
figured out, I'll probably submit a fairly hefty patch to that file  
to add additional documentation.

> Also, books Linux Kernel Development and Understanding the Linux  
> Kernel have fairly good information on VFS (and related) stuff.

Ah, thanks again!  It looks like both of those are available through  
my university's Safari/ProQuest subscription (http:// 
safari.oreilly.com/), so I'll take a look right away!

Cheers,
Kyle Moffett

--
I lost interest in "blade servers" when I found they didn't throw  
knives at people who weren't supposed to be in your machine room.
   -- Anthony de Boer



  reply	other threads:[~2006-01-23 17:51 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-22  6:42 soft update vs journaling? John Richard Moser
2006-01-22  8:51 ` Jan Engelhardt
2006-01-22 18:40   ` John Richard Moser
2006-01-22 19:05   ` Adrian Bunk
2006-01-22 19:08     ` Arjan van de Ven
2006-01-22 19:25       ` Adrian Bunk
2006-01-24  2:33       ` Jörn Engel
2006-01-22  9:31 ` Theodore Ts'o
2006-01-22 18:54   ` John Richard Moser
2006-01-22 21:02     ` Theodore Ts'o
2006-01-22 22:44       ` Kyle Moffett
2006-01-23  7:24         ` Theodore Ts'o
2006-01-23 13:31           ` Mitchell Blank Jr
2006-01-23 13:33           ` Kyle Moffett
2006-01-23 13:52             ` Antonio Vargas
2006-01-23 16:48               ` Linux VFS architecture questions Kyle Moffett
2006-01-23 17:00                 ` Pekka Enberg
2006-01-23 17:50                   ` Kyle Moffett [this message]
2006-01-23 17:54                     ` Randy.Dunlap
2006-01-23 20:48           ` soft update vs journaling? Folkert van Heusden
2006-01-23  1:02       ` John Richard Moser
2006-01-22 19:50   ` Diego Calleja
2006-01-22 20:39     ` Suleiman Souhlal
2006-01-22 20:50       ` Diego Calleja
2006-01-23  1:00     ` John Richard Moser
2006-01-23  1:09       ` Suleiman Souhlal
2006-01-23  2:09         ` John Richard Moser
2006-01-22 19:26 ` James Courtier-Dutton
2006-01-23  0:06   ` John Richard Moser
2006-01-23  5:32 ` Michael Loftis
2006-01-23 18:52   ` John Richard Moser
2006-01-23 19:32     ` Matthias Andree

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=A31CA9FF-4B56-483C-8BCC-CECD9B812844@mac.com \
    --to=mrmacman_g4@mac.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigelenki@comcast.net \
    --cc=penberg@cs.helsinki.fi \
    --cc=tytso@mit.edu \
    --cc=windenntw@gmail.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).