From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: linux-kernel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, netdev@vger.kernel.org
Subject: [0/3] The new POHMELFS release.
Date: Wed, 8 Oct 2008 01:19:25 +0400 [thread overview]
Message-ID: <20081007211925.GA1274@2ka.mipt.ru> (raw)
Hello.
I'm pleased to announce the new POHMELFS release.
This is a major change in the Parallel Optimized Host Message Exchange
Layered File System: completely rewritten distributed (byte-range)
locking subsystem. Locks are actually byte-range, but since every Linux
FS locks the whole inode, POHMELFS locks also do this. Multiple writers
are somewhat serialized and thus cache is coherent (pages either contain
valid data or they are not uptodate) on all clients at any time.
Other changes made in this release:
* Documentation update. Fixed by Adam Langley (agl_imperialviolet.org)
* Add/del/show commands patch from Varun Chandramohan
(varunc_linux.vnet.ibm.com)
* Bug fixes and cleanups.
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:
* Local coherent cache for data and metadata.
* 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.
POHMELFS roadmap now includes distributed and parallel facilities of the
server.
1. POHMELFS homepage.
http://tservice.net.ru/~s0mbre/old/?section=projects&item=pohmelfs
2. POHMELFS archive.
http://tservice.net.ru/~s0mbre/archive/pohmelfs/
3. GIT trees.
http://tservice.net.ru/~s0mbre/cgi-bin/gitweb.cgi
4. Development status.
http://tservice.net.ru/~s0mbre/blog//devel/fs
--
Evgeniy Polyakov
next reply other threads:[~2008-10-07 21:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 21:19 Evgeniy Polyakov [this message]
2008-10-07 21:20 ` [1/3] POHMELFS: vfs changes Evgeniy Polyakov
2008-10-07 21:21 ` [2/3] POHMELFS: documentation Evgeniy Polyakov
2008-10-07 21:21 ` [3/3] POHMELFS: core 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=20081007211925.GA1274@2ka.mipt.ru \
--to=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 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).