From: Pavel Machek <pavel@suse.cz>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [2/3] POHMELFS: Documentation.
Date: Sat, 12 Jul 2008 09:01:51 +0200 [thread overview]
Message-ID: <20080712070150.GD13483@ucw.cz> (raw)
In-Reply-To: <20080707181019.GC15687@2ka.mipt.ru>
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
next prev parent reply other threads:[~2008-07-12 7:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 18:07 [0/3] POHMELFS high performance network filesystem. First steps in parallel processing Evgeniy Polyakov
2008-07-07 18:08 ` [1/3] POHMELFS: VFS trivial change Evgeniy Polyakov
2008-07-07 18:10 ` [2/3] POHMELFS: Documentation Evgeniy Polyakov
2008-07-12 7:01 ` Pavel Machek [this message]
2008-07-12 7:26 ` Evgeniy Polyakov
2008-07-07 18:11 ` [3/3] POHMELFS: core files Evgeniy Polyakov
2008-07-07 18:15 ` [0/3] POHMELFS high performance network filesystem. Strong crypto support Evgeniy Polyakov
-- strict thread matches above, loose matches on Subject: below --
2008-10-07 21:19 [0/3] The new POHMELFS release Evgeniy Polyakov
2008-10-07 21:21 ` [2/3] POHMELFS: documentation Evgeniy Polyakov
2008-06-13 16:37 [0/3] POHMELFS high performance network filesystem. First steps in parallel processing Evgeniy Polyakov
2008-06-13 16:41 ` [2/3] POHMELFS: Documentation Evgeniy Polyakov
2008-06-14 2:15 ` Jamie Lokier
2008-06-14 6:56 ` Evgeniy Polyakov
2008-06-14 9:49 ` Jeff Garzik
2008-06-14 18:45 ` Trond Myklebust
2008-06-14 19:25 ` Evgeniy Polyakov
2008-06-15 4:27 ` Sage Weil
2008-06-15 5:57 ` Evgeniy Polyakov
2008-06-15 16:41 ` Sage Weil
2008-06-15 17:50 ` Evgeniy Polyakov
2008-06-16 3:17 ` Sage Weil
2008-06-16 10:20 ` Evgeniy Polyakov
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=20080712070150.GD13483@ucw.cz \
--to=pavel@suse.cz \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.