From: Evgeniy Polyakov <zbr@ioremap.net>
To: Pavel Machek <pavel@suse.cz>
Cc: Evgeniy Polyakov <zbe@ioremap.net>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, pohmelfs@ioremap.net,
netdev@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [1/9] pohmelfs: documentation.
Date: Sun, 28 Dec 2008 16:41:55 +0300 [thread overview]
Message-ID: <20081228134155.GB858@ioremap.net> (raw)
In-Reply-To: <20081226192219.GB1761@ucw.cz>
Hi Pavel.
On Fri, Dec 26, 2008 at 08:22:20PM +0100, Pavel Machek (pavel@suse.cz) wrote:
> > + * Flexible object architecture optimized for network processing.
> > + Ability to create long paths to objects and remove arbitrarily huge
> > + directories with a single network command.
> > + (like removing the whole kernel tree via a single network
> > command).
>
> Hmm, so we'll need new unlink_recursively() syscall?
If we could have it, it would be really simple in POHMELFS :)
> > + * Very high performance.
>
> Do you have some nfs comparison?
Alot (nfs, xfs, pohmelfs with crypto, data and metadata IO)...
http://tservice.net.ru/~s0mbre/blog/devel/fs/2008_06_13_1.html
http://tservice.net.ru/~s0mbre/blog/devel/fs/2008_07_07.html
http://tservice.net.ru/~s0mbre/blog/devel/fs/2008_06_25.html
http://tservice.net.ru/~s0mbre/blog/devel/fs/2008_06_19_1.html
One can find more at old development track:
http://tservice.net.ru/~s0mbre/blog//devel/fs
--
Evgeniy Polyakov
next prev parent reply other threads:[~2008-12-28 13:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-26 14:18 [0/9] pohmelfs: The Great Southern Trendkill release Evgeniy Polyakov
2008-12-26 14:18 ` [1/9] pohmelfs: documentation Evgeniy Polyakov
2008-12-26 14:18 ` [2/9] pohmelfs: configuration interface Evgeniy Polyakov
2008-12-26 14:18 ` [3/9] pohmelfs: crypto processing Evgeniy Polyakov
2008-12-26 14:18 ` [4/9] pohmelfs: directory operations Evgeniy Polyakov
2008-12-26 14:18 ` [5/9] pohmelfs: inode operations Evgeniy Polyakov
2008-12-26 14:18 ` [6/9] pohmelfs: distributed locking and cache coherency protocol Evgeniy Polyakov
2008-12-26 14:18 ` [7/9] pohmelfs: network operations Evgeniy Polyakov
2008-12-26 14:18 ` [8/9] pohmelfs: transaction layer Evgeniy Polyakov
2008-12-26 14:18 ` [9/9] pohmelfs: kconfig/makefile and vfs changes Evgeniy Polyakov
2008-12-26 19:22 ` [1/9] pohmelfs: documentation Pavel Machek
2008-12-28 13:41 ` Evgeniy Polyakov [this message]
2008-12-28 22:19 ` Paolo Ciarrocchi
2008-12-30 21:23 ` Evgeniy Polyakov
2008-12-26 19:26 ` [0/9] pohmelfs: The Great Southern Trendkill release Pavel Machek
2008-12-28 13:53 ` Evgeniy Polyakov
-- strict thread matches above, loose matches on Subject: below --
2009-02-09 14:02 [0/9] pohmelfs for drivers/staging Evgeniy Polyakov
2009-02-09 14:02 ` [1/9] pohmelfs: documentation 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=20081228134155.GB858@ioremap.net \
--to=zbr@ioremap.net \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=pohmelfs@ioremap.net \
--cc=zbe@ioremap.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).