From: Evgeniy Polyakov <zbr@ioremap.net>
To: linux-kernel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, netdev@vger.kernel.org
Subject: [0/3] POHMELFS: the new release. Extended attributes.
Date: Thu, 23 Oct 2008 22:54:35 +0400 [thread overview]
Message-ID: <20081023185435.GA18461@2ka.mipt.ru> (raw)
Hello.
I'm pleased to announce the new POHMELFS release.
Short changelog:
* Extended attributes.
* Distributed locks for metadata updates.
* Bug fixes and cleanups ( i n c l u d i n g w h i t e s p a c e s ! ).
POHMELFS is a very high performance parallel network filesystem with
local coherent cache of data and metadata. Its main goal is distributed
processing of the data.
Features supported by POHMELFS:
* Locally coherent cache for data and metadata with (potentially) byte-range locks.
Since all Linux filesystems lock the whole inode during writing, algorithm
is very simlpe and does not use byte-ranges, although they are sent in
locking messages.
* Completely async processing of all events (hard and symlinks are the
only exceptions) including object creation and data reading and
writing.
* Flexible object architecture optimized for network processing. Ability
to create long pathes to object and remove arbitrary huge
directories in single network command.
* High performance is one of the main design goals.
* Very fast and scalable multithreaded userspace server. Being in
userspace it works with any underlying filesystem and still is much
faster than async in-kernel NFS one.
* Transactions support. Full failover for all operations. Resending
transactions to different servers on timeout or error.
* Client is able to switch between different servers (if one goes down,
client automatically reconnects to second and so on).
* Client parallel extensions: ability to write to multiple servers and
balance reading between them.
* Client dynamical server reconfiguration: ability to add/remove servers
from working set in run-time.
* Strong authentification and possible data encryption in network channel.
* Extended attributes support.
POHMELFS roadmap now includes distributed and parallel facilities of the
server.
1. POHMELFS homepage.
http://www.ioremap.net/node/21
2. POHMELFS archive.
http://www.ioremap.net/archive/pohmelfs/
3. GIT trees.
http://www.ioremap.net/cgi-bin/gitweb.cgi
4. Development status.
http://www.ioremap.net/taxonomy/term/4
--
Evgeniy Polyakov
next reply other threads:[~2008-10-23 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 18:54 Evgeniy Polyakov [this message]
2008-10-23 18:56 ` [1/3] POHMELFS: Documentation Evgeniy Polyakov
2008-10-27 15:05 ` Michael Kerrisk
2008-10-27 16:17 ` Evgeniy Polyakov
2008-10-23 18:56 ` [2/3] POHMELFS: Core Evgeniy Polyakov
2008-10-23 18:57 ` [3/3] POHMELFS: VFS changes (2 exports) 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=20081023185435.GA18461@2ka.mipt.ru \
--to=zbr@ioremap.net \
--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.