From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: POHMELFS high performance network filesystem release.
Date: Sat, 26 Apr 2008 01:03:15 +0400 [thread overview]
Message-ID: <20080425210315.GA3712@2ka.mipt.ru> (raw)
In-Reply-To: <87wsmlx2w1.fsf@basil.nowhere.org>
Hi.
On Fri, Apr 25, 2008 at 07:25:50PM +0200, Andi Kleen (andi@firstfloor.org) wrote:
> Evgeniy Polyakov <johnpol@2ka.mipt.ru> writes:
>
> > It is work-in-progress, and network protocol is not stable yet.
>
> Congratulations. I'm sure it was a lot of work.
Well, not _that_ lot of work, but it is interesting, so...
It was at least once time rewriten mostly from scratch to allow all those
shiny things. It is not in-advance design, but kind of evolution based
on my filesystem studying.
> But could you please quickly expand how useful it is at this state? Is
> it already far enough that someone could save some data on it and use
> it without it crashing all the time?
>
> It's unclear even from your status report.
Well, it does not crash in iozone, huge untar, kernel compilations
and big file copies. And it works reliably enough to make md5 sums be
equal on both server and clients, but I will not be surprised if it
contains some bugs. I also will not be surprised, if current server
behaviour does not match POSIX expectations (I'm curios of NFS
matches that), but at least this behaviour will be much more clean
with transaction introduction and server support for them.
So, it works for usual NFS-like workload, but since it is rather young
FS (this particular design implementation exists for about couple of
months), there may be some questions...
Getting that POHMELFS is really simple and its design is oriented to be
as open as possible without burden of old age problems and
compatibilities, it is not a any kind of a problem to locate and fix a
bug, so I'm very open for any kind of reports.
--
Evgeniy Polyakov
prev parent reply other threads:[~2008-04-25 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-25 15:07 POHMELFS high performance network filesystem release Evgeniy Polyakov
2008-04-25 17:25 ` Andi Kleen
2008-04-25 21:03 ` 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=20080425210315.GA3712@2ka.mipt.ru \
--to=johnpol@2ka.mipt.ru \
--cc=andi@firstfloor.org \
--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).