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: Sat, 29 Jul 2006 18:30:23 +0200 [thread overview]
Message-ID: <9615ac9b0607290930i1aa35776nfbe773c4d8e93b5c@mail.gmail.com> (raw)
In-Reply-To: <20060729071507.59949.qmail@web37511.mail.mud.yahoo.com>
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?)
> In addition I want to find out whether these address space
> operations are for performance reasons or are mandatory to
> implement.
No, I guess you could access the underlying device (or a remote
server) each time a filesystem object is read or written to. This
approach would be simple but
a) it could be very slow (at least a block device based filesystem
like that would),
b) you basically wouldn't be able to implement mmap unless you wrote
an equivalent of the page cache and
c) when you use the generic functions to handle the file operations
and only code the address space operations, it is not that much
more difficult.
> In addition do distributed file systems on the client
> and server side require to implement address space
> operations e.g. nfs (client side) implements these
> address space operations.
I'm not an expert on network filesystems but it would probably depend
on whether and what kind of client caching you want.
HTH
Martin
next prev parent reply other threads:[~2006-07-29 16:30 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 [this message]
2006-08-01 5:46 ` UZAIR LAKHANI
2006-08-01 16:56 ` Bryan Henderson
2006-08-01 16:58 ` Martin Jambor
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=9615ac9b0607290930i1aa35776nfbe773c4d8e93b5c@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).