Re: [1/9] pohmelfs: documentation.

[Pavel Machek]

Hi!

> +Homepage: http://www.ioremap.net/projects/pohmelfs
> +
> +POHMELFS first began as a network filesystem with coherent local data and
> +metadata caches but is now evolving into a parallel distributed filesystem.
> +
> +Main features of this FS include:
> + * 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 simple and does not use byte-ranges, although they are sent in
> +	locking messages.
> + * Completely async processing of all events except creation of hard and symbolic
> +	links, and rename events.
> +	Object creation and data reading and writing are processed asynchronously.
> + * 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?

> + * Very high performance.

Do you have some nfs comparison?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/