Re: Communicating FileSystem Structures b/w Two Machines

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 4/10/06, UZAIR LAKHANI <uzairr_bs1b@xxxxxxxxx> wrote:
>
<snip>
> In order for client and server to communicate, they
> have to exchange different structures like
> super-block, inode, dentry, vfsmount etc. We have to
> use 2.6.x kernels but since different versions of
> kernel will have differnt sizes for these structures,
> I am getting problems in communicating these
> structures b/w client and server. I therefore want a
> machine and kernel independent way for communicating
> these structures so as to handle the sizes problem.
>

As Martin Jambor already gave some good points for structure size
problems among different machines and I just want to add one more
thing:

Why are you going to transfer superblock, inodes, dentries etc ? I
think you just need to transfer the information necessary (meta-data)
(like permissions, directory structure etc) between client/server
besides the actual file data. And for this you need to create a proper
protocol which you actually send as a payload in TCP/IP or other
protocol packet (you can get idea from NFS's protocol)

I hope this helps

--
Fawad Lateef
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux