Messages in this thread |  | | | Date | Sat, 12 Jul 2008 11:26:10 +0400 | | From | Evgeniy Polyakov <> | | Subject | Re: [2/3] POHMELFS: Documentation. | |
Hi.
On Sat, Jul 12, 2008 at 09:01:51AM +0200, Pavel Machek (pavel@suse.cz) wrote:
> > + * 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 ...) ?
There are people who belive that most with exceptions is still all :)
Actually I think that if there are exceptions, than it is not 'all'.
> > +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?
Big endian in the network. CPU endian on both ends.
--
Evgeniy Polyakov
|  |