From: Craig Dunwoody <cdunwoody@graphstream.com>
To: linux-kernel@vger.kernel.org
Cc: cdunwoody@graphstream.com
Subject: Re: [GIT PULL] Ceph distributed file system client for 2.6.33
Date: Sun, 27 Dec 2009 16:17:50 -0800 [thread overview]
Message-ID: <27445.1261959470@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
next reply other threads:[~2009-12-28 0:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-28 0:17 Craig Dunwoody [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-12-07 23:25 [GIT PULL] Ceph distributed file system client for 2.6.33 Sage Weil
2009-12-18 20:54 ` Sage Weil
2009-12-18 21:38 ` Linus Torvalds
2009-12-18 23:15 ` Jim Garlick
2009-12-19 11:01 ` Andi Kleen
2009-12-21 16:42 ` Sage Weil
2010-02-09 20:43 ` Josef Bacik
2009-12-19 5:33 ` Valdis.Kletnieks
2009-12-21 16:42 ` Sage Weil
2009-12-21 18:04 ` Andreas Dilger
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=27445.1261959470@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.