From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Fawad Lateef" <fawadlateef@gmail.com>
Subject: Re: Regarding a Simple Version of nfs & nfsd
Date: Tue, 21 Mar 2006 20:27:32 +0500
Message-ID: <1e62d1370603210727q712c0cb9q2f17b2b6b42e48d9@mail.gmail.com>
References: <20060320041858.46219.qmail@web37909.mail.mud.yahoo.com>
	 <1142896246.2914.5.camel@ool-44c32f98.dyn.optonline.net>
	 <1e62d1370603210109t4910bc59ra817db695ed4c41c@mail.gmail.com>
	 <1142946374.13939.9.camel@ool-44c32f98.dyn.optonline.net>
	 <1e62d1370603210533m6271459h7027e394ef008e46@mail.gmail.com>
	 <1142953747.13325.11.camel@rockstar.fsl.cs.sunysb.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Cc: "UZAIR LAKHANI" <uzairr_bs1b@yahoo.com>,
	linux-fsdevel@vger.kernel.org
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from zeus2.kernel.org ([204.152.191.36]:44772 "EHLO zeus2.kernel.org")
	by vger.kernel.org with ESMTP id S1751772AbWCUP3f convert rfc822-to-8bit
	(ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
	Tue, 21 Mar 2006 10:29:35 -0500
Received: from nproxy.gmail.com (nproxy.gmail.com [64.233.182.198])
	by zeus2.kernel.org (8.13.1/8.13.1) with ESMTP id k2LFTXAc010421
	for <linux-fsdevel@vger.kernel.org>; Tue, 21 Mar 2006 15:29:34 GMT
Received: by nproxy.gmail.com with SMTP id o60so992677nfa
        for <linux-fsdevel@vger.kernel.org>; Tue, 21 Mar 2006 07:27:33 -0800 (PST)
To: "Avishay Traeger" <atraeger@cs.sunysb.edu>
In-Reply-To: <1142953747.13325.11.camel@rockstar.fsl.cs.sunysb.edu>
Content-Disposition: inline
Sender: linux-fsdevel-owner@vger.kernel.org
List-Id: linux-fsdevel.vger.kernel.org

On 3/21/06, Avishay Traeger <atraeger@cs.sunysb.edu> wrote:
>
> When you deal with stackable file systems, the "lower-level file system"
> is the file system that you stack on top of.  So usually you have a
> request come in through the VFS, into the stackable file system, and
> then to the lower-level file system.  The way I see the design, you have
> a stackable file system "simplenfs" over another file system
> "lowerfs" (excuse the poor ascii art):
>
>  |
>  | sys_read()
>  |
> \_/
> VFS
>  |
>  | simplenfs_read()
>  |
> \_/
> simplenfs ---> sends read request to server
>  .
>  .
>  .
> \_/
> lowerfs
>
>
> When simplenfs gets the reply from the server, it returns it to the VFS.
> My question is what does lowerfs do if simplenfs is doing all the
> communications with the server.
>

Let me re-draw the diagram you mentioned with my idea. The ascii art :)

Client Side
     |
sys_read
     |
   vfs
     |
 client fs    ................... The fs running on client side, doing
nothing by itself, but provide support of mounting/unmounting,
readin/writing etc to client os
     |
  LAN
     |
stackable fs  .......... or you can say server daemon (accessing the real fs)
     |
   vfs
     |
  ext2

I hope now I able to make you clear my idea. Or you can suggest any
better than this. (I am just interested, not going to make this kind
of FS as don't have time. But your idea might help the person asking
question (Uzair))


--
Fawad Lateef