From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: [2/3] POHMELFS: Documentation. Date: Sat, 12 Jul 2008 09:01:51 +0200 Message-ID: <20080712070150.GD13483@ucw.cz> References: <20080707180736.GA15687@2ka.mipt.ru> <20080707181019.GC15687@2ka.mipt.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org, linux-fsdevel@vger.kernel.org To: Evgeniy Polyakov Return-path: Received: from gprs189-60.eurotel.cz ([160.218.189.60]:2588 "EHLO spitz.ucw.cz" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751750AbYGLHHJ (ORCPT ); Sat, 12 Jul 2008 03:07:09 -0400 Content-Disposition: inline In-Reply-To: <20080707181019.GC15687@2ka.mipt.ru> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Hi! > + * Completely async processing of all events (hard, symlinks and rename are the > + only exceptions) including object creation and data reading and writing. Hmm... this is little funny. Async processing of most events (only exceptions are ...) ? > +POHMELFS network protocol. > + > +Basic structure used in network communication is following command: > + > +struct netfs_cmd > +{ > + __u16 cmd; /* Command number */ > + __u16 csize; /* Attached crypto information size */ > + __u16 cpad; /* Attached padding size */ > + __u16 ext; /* External flags */ > + __u32 size; /* Size of the attached data */ > + __u32 trans; /* Transaction id */ > + __u64 id; /* Object ID to operate on. Used for feedback.*/ > + __u64 start; /* Start of the object. */ > + __u64 iv; /* IV sequence */ > + __u8 data[0]; > +}; Which endianity? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html