From: Steve French <smfrench@austin.rr.com>
To: linux-kernel@vger.kernel.org, stephane.wirtel@belgacom.net
Subject: Re: Documenting the VFS
Date: Sat, 13 Aug 2005 15:47:28 -0500 [thread overview]
Message-ID: <42FE5C60.6000107@austin.rr.com> (raw)
> Where can I found an up to date documentation about the VFS interface?
There is an ok chapter on filesystems in the O'Reilly Linux Kernel book,
and the Linux Device Drivers book (also from O'Reilly) is essential
reading.
Pay careful attention to fs/libfs.c and the nice small fs fs/ramfs which calls
libfs which are both useful as they help understand the minimum that certain
vfs interfaces require. This was helpful to me when I wrote the cifs
filesystem.
Documentation/filesystems/vfs.txt has a little bit of documentation, as
does Documentation/Locking and Documentation/directory-locking.
I may try to write something (perhaps articles?) longer and
more formal if I get time.
Finally the lwn series (weekly articles) on kernel development is
invaluable in describing what changes.
next reply other threads:[~2005-08-13 20:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-13 20:47 Steve French [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-13 19:05 Documenting the VFS Guillermo López Alejos
2005-08-13 19:55 ` Stephane Wirtel
2005-08-18 7:55 ` Daniel Phillips
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=42FE5C60.6000107@austin.rr.com \
--to=smfrench@austin.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stephane.wirtel@belgacom.net \
/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