From: Jim Garlick <garlick@llnl.gov>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sage Weil <sage@newdream.net>,
Gregory Haskins <gregory.haskins@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [GIT PULL] Ceph distributed file system client for 2.6.33
Date: Fri, 18 Dec 2009 15:15:05 -0800 [thread overview]
Message-ID: <20091218231505.GA21371@llnl.gov> (raw)
In-Reply-To: <alpine.LFD.2.00.0912181327200.3712@localhost.localdomain>
On Fri, Dec 18, 2009 at 01:38:00PM -0800, Linus Torvalds wrote:
> On Fri, 18 Dec 2009, Sage Weil wrote:
> >
> > I would still like to see ceph merged for 2.6.33. It's certainly not
> > production ready, but it would be greatly beneficial to be in mainline for
> > the same reasons other file systems like btrfs and exofs were merged
> > early.
>
> The best thing to do is to try to have users that are vocal about the
> feature, and talk about how great it is. Some advocates for it, in other
> words. Just a few other people saying "hey, I use this, it's great", is
> actually a big deal to me. For alacrityvm and cephfs, I didn't have that,
> or they just weren't loud enough for me to hear.
FWIW: I'd like to see it go in.
Ceph is new and experimental so you're not going to see production shops
like ours jumping up and down saying we use it and are tired of merging it,
like we would say if if Lustre were (again) on the table.
However I will say Ceph looks good and in the interest of nuturing future
options, I'm for merging it!
Jim Garlick
Lawrence Livermore National Laboratory
next prev parent reply other threads:[~2009-12-18 23:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2009-12-28 0:17 Craig Dunwoody
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=20091218231505.GA21371@llnl.gov \
--to=garlick@llnl.gov \
--cc=akpm@linux-foundation.org \
--cc=gregory.haskins@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sage@newdream.net \
--cc=torvalds@linux-foundation.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