netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: [0/9] pohmelfs: The Great Southern Trendkill release.
Date: Sun, 28 Dec 2008 16:53:31 +0300	[thread overview]
Message-ID: <20081228135331.GC858@ioremap.net> (raw)
In-Reply-To: <20081226192618.GC1761@ucw.cz>

Hi Pavel.

On Fri, Dec 26, 2008 at 08:26:19PM +0100, Pavel Machek (pavel@suse.cz) wrote:
> > POHMELFS is a kernel client for the developed distributed parallel internet
> > filesystem. As it exists today, it is a high-performance parallel network
> > filesystem with ability to balance reading from multiple hosts and simultaneously
> > write data to multiple hosts.
> 
> So ocfs2 -alike fs?

I think POHMELFS is more like pNFS now (yet), kernel client does not
get into similar to ocfs distributed facilities. POHMELFS server is
rather simple right now and when it will be ready with own distributed
design it will be very different from what we have in kernel.
Distributed processing engine is being built with distributed hash
table design in mind, so there will be no need for any kind of
metadata servers, locking daemons or special node management controls.

> > Signed-off-by: Evgeniy Polyakov <zbr@ioremap.net>
> 
> Do you think its ready for -mm?
> 
> Can it survive test such as paralel kernel compilation(s), fsx, etc?

I did not run fsx but kernel compilations, iozone, bonnie and the like
benchmarks run without any problems on the mounted partitions in my
test lab. There will be some extensions to the network protocol (mainly
new commands to force client to connect to the diferent server when
current one asks for that), but except that I do not have any
additional complex extensions in design. So I consider this kernel
client as mostly ready.

> How fast is it compared to nfs? to ext3 over fast network?

I ran really lots of tests and POHMELFS performance is frequently way
ahead of what async NFS provides, but this of course depends on the
final workload and probably may have some drawbacks found.

Links with graphs and numbers were sent in the another mail.

-- 
	Evgeniy Polyakov

      reply	other threads:[~2008-12-28 13:53 UTC|newest]

Thread overview: 16+ 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
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 [this message]

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=20081228135331.GC858@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).