|| ||Evgeniy Polyakov <email@example.com>|
|| ||[0/3] POHMELFS high performance network filesystem. First steps in parallel processing.|
|| ||Mon, 7 Jul 2008 22:07:36 +0400|
|| ||firstname.lastname@example.org, email@example.com|
I'm pleased to announce POHMEL high performance network parallel distributed filesystem.
POHMELFS stands for Parallel Optimized Host Message Exchange Layered File System.
Development status can be tracked in filesystem section .
This is a high performance network filesystem with local coherent cache of data
and metadata. Its main goal is distributed parallel processing of data.
System supports strong transaction model with failover recovery, allows to
encrypt/hash whole data channel and perform read load balancing and
write to multiple servers in parallel.
This release brings following features:
* Strong crypto support. One can specify encryption method (like
cbc(aes), hash or digest, or all of them to be performed on
whole data channel (except headers). If special mount option is
specified, then mount will file if server does not support
requested by client crypto options. By defalt that crypto
options will be skipped.
* Bug fixes.
Very likely it is one of the last non-bug-fixing release of the kernel
client side, next release will incorporate features, needed for distributed
parallel data processing (like ability to add new servers via network
command from another servers), so most of the work will be devoted to server
Basic POHMELFS features:
* Local coherent (notes ) cache for data and metadata).
* Completely async processing of all events (hard and symlinks are the only
exceptions) including object creation and data reading/writing.
* Flexible object architecture optimized for network processing. Ability to
create long pathes to object and remove arbitrary huge directoris 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 ni-kernel NFS one.
* Client is able to switch between different servers (if one goes down,
client automatically reconnects to second and so on).
* Transactions support. Full failover for all operations. Resending
transactions to different servers on timeout or error.
* Strong encryption and/or hashing of the data channel with
autoconfiguration of the server/client supported crypto algorithms.
* Server redundancy extensions (ability to store data in multiple locations
according to regexp rules, like '*.txt' in /root1 and '*.jpg' in /root1
* Async writing of the data from receiving kernel thread into userspace
pages via copy_to_user() (check development tracking blog for results).
* Client dynamical server reconfiguration: ability to add/remove servers
from working set by server command (as part of development distributed
* Generic parallel distributed server algorithms.
One can grab sources from archive or git  or check homepage .
1. POHMELFS development status.
2. Source archive.
3. POHMELFS homepage.
4. POHMELFS vs NFS benchmark [iozone results are coming].
Plain async NFS vs sha1+cbc(aes) POHMELFS
5. Cache-coherency notes.
Signed-off-by: Evgeniy Polyakov <firstname.lastname@example.org>
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html