public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Craig Dunwoody <cdunwoody@graphstream.com>
To: linux-kernel@vger.kernel.org
Cc: cdunwoody@graphstream.com
Date: Sun, 27 Dec 2009 13:06:19 -0800	[thread overview]
Message-ID: <24388.1261947979@n20.hq.graphstream.com> (raw)


sage weil writes (2009/12/21):
>If you want stability, then it's probably too early to merge.  If you
>want active users, that essentially hinges on stability too.  But if
>it's interest in/demand for an alternative distributed fs, then the
>sooner it's merged the better.

I understand there are many considerations about when to merge something
new, but in general would like to see the Ceph client merged sometime
soon.

In my view, there is a wide range of applications for which Ceph has
the potential to be significantly more efficient than the other
distributed file systems that I know about.

Ceph has a solid architecture and a small but strong dev team.  I
believe that the project is now at a point where wider-scale testing
can greatly accelerate progress toward production-level usability.
Having the client in mainline will help reduce barriers to such
testing.

Craig Dunwoody
GraphStream Incorporated


                 reply	other threads:[~2009-12-27 21:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=24388.1261947979@n20.hq.graphstream.com \
    --to=cdunwoody@graphstream.com \
    --cc=linux-kernel@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