From: Andi Kleen <andi@firstfloor.org>
To: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: POHMELFS high performance network filesystem release.
Date: Fri, 25 Apr 2008 19:25:50 +0200 [thread overview]
Message-ID: <87wsmlx2w1.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20080425150756.GA28369@2ka.mipt.ru> (Evgeniy Polyakov's message of "Fri, 25 Apr 2008 19:07:56 +0400")
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.
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.
-Andi
next prev parent reply other threads:[~2008-04-25 17:28 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 [this message]
2008-04-25 21:03 ` 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=87wsmlx2w1.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=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).