linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Mason <clm@fb.com>
To: Jonathan Corbet <corbet@lwn.net>, Marc MERLIN <marc@merlins.org>
Cc: <linux-btrfs@vger.kernel.org>
Subject: Re: Which companies contribute to Btrfs?
Date: Mon, 28 Apr 2014 17:06:33 -0400	[thread overview]
Message-ID: <535EC2D9.9000609@fb.com> (raw)
In-Reply-To: <20140428150006.087c2357@lwn.net>

On 04/28/2014 03:00 PM, Jonathan Corbet wrote:
> On Wed, 23 Apr 2014 18:18:34 -0700
> Marc MERLIN <marc@merlins.org> wrote:
>
>> I writing slides about btrfs for an upcoming talk (at linuxcon) and I was
>> trying to gather a list of companies that contribute code to btrfs.
>
> So I just ran into this now.  I did a quick gitdm run over the entire btrfs
> history in the kernel and came up with this:
>
> 	Top changeset contributors by employer
> 	Oracle                    1249 (33.2%)
> 	Fujitsu                    613 (16.3%)
> 	Red Hat                    483 (12.8%)
> 	Fusion-IO                  296 (7.9%)
> 	(None)                     288 (7.6%)
> 	Novell                     203 (5.4%)
> 	STRATO AG                  152 (4.0%)
> 	Couchbase                  106 (2.8%)
> 	(Consultant)                62 (1.6%)
> 	(Unknown)                   54 (1.4%)
> 	Intel                       48 (1.3%)
> 	New Dream Network           36 (1.0%)
> 	Facebook                    31 (0.8%)
> 	IBM                         20 (0.5%)
> 	FOSS Outreach Program for Women   12 (0.3%)
> 	Google                      12 (0.3%)
> 	(Academia)                  11 (0.3%)
> 	Parallels                   11 (0.3%)
> 	HP                          10 (0.3%)
> 	Datera Inc.                  5 (0.1%)
>
> I would expect the rankings to change a bit in the near future, if those
> slackers at Facebook ever get it in gear...:)

Grin, Josef has taken a few weeks off to look after the newly released 
Josefv3.

We've got the pool of web servers on btrfs at 800 now, and soon I'm sure 
it'll start kicking out some fun bugs.

Once we get the btrfs tier up to 1000, I'll have a second slice of 1000 
machines running 3.14 as well (or whatever the current linus rev is).

Those will be btrfs too, I expect the crash recovery code will get quite 
a bit of testing.

-chris

  reply	other threads:[~2014-04-28 21:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-24  1:18 Which companies contribute to Btrfs? Marc MERLIN
2014-04-24  1:19 ` Which companies are using Btrfs in production? Marc MERLIN
2014-04-24  7:13   ` Adam Brenner
2014-04-24 12:34   ` Austin S. Hemmelgarn
2014-04-24 12:52   ` Tomasz Torcz
2014-04-24 13:34   ` Daniel Lee
2014-04-24 21:41     ` Marc MERLIN
2014-04-24 22:03     ` Justin Maggard
2014-04-24 23:14       ` Marc MERLIN
2014-04-25 14:47         ` David Sterba
2014-04-25 15:01           ` Chris Mason
2014-04-25 15:20           ` Marc MERLIN
2014-04-25 15:32             ` ronnie sahlberg
2014-04-28 14:16             ` David Sterba
2014-04-28 15:01             ` Eric Sandeen
2014-04-24  2:29 ` Which companies contribute to Btrfs? Eric Sandeen
2014-04-24  2:30 ` Eric Sandeen
2014-04-24  3:45   ` Marc MERLIN
2014-04-24  4:32     ` Eric Sandeen
2014-04-24 10:31 ` Filipe David Manana
2014-04-24 17:07   ` Marc MERLIN
2014-04-24 11:39 ` David Sterba
2014-04-24 12:55   ` Fajar A. Nugraha
2014-04-24 21:41     ` Marc MERLIN
2014-04-28 19:00 ` Jonathan Corbet
2014-04-28 21:06   ` Chris Mason [this message]
2014-04-29  0:06   ` Chester
2014-04-29  0:08     ` Marc MERLIN
2014-04-29  0:55     ` Chris Mason

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=535EC2D9.9000609@fb.com \
    --to=clm@fb.com \
    --cc=corbet@lwn.net \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=marc@merlins.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).