From: Theodore Ts'o <tytso@mit.edu>
To: Wuqixuan <wuqixuan@huawei.com>
Cc: "adilger@sun.com" <adilger@sun.com>, "tm@tao.ma" <tm@tao.ma>,
"xiaoqiangnk@gmail.com" <xiaoqiangnk@gmail.com>,
Lizefan <lizefan@huawei.com>,
"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Help to know the stable ver of ext4 for commercial app.
Date: Fri, 1 Feb 2013 22:23:07 -0500 [thread overview]
Message-ID: <20130202032307.GA16364@thunk.org> (raw)
In-Reply-To: <BB7C62C2B0732E4DA93834A501E8464544E6181A@SZXEML519-MBS.china.huawei.com>
On Sat, Feb 02, 2013 at 02:30:11AM +0000, Wuqixuan wrote:
>
> Currently we are choocing ssd/sata file system using for stream media application. We are using 2.6.34.10 (can be upgraded to 2.6.34.14). We are consider of ext3 or ext4. Even in wikipedia, it mentions ext4 is stable from 2.6.28, I still have some doubts:
>
> 1. Whether 2.6.34.10 of ext4 is stable enough for commercial use or not.
> 2. Are there many mature commercial application on ext4 on 2.6.34.10 or before? Can tell some famous company or app name ?
Well, it's _possible_ to use 2.6.34 as a base for a production server.
Red Hat's RHEL 5 was based on kernel of approximately that vintage
(with many, many patches). Google announced it was upgrading its data
centers to use ext4 just about the time I was hired at Google[1], in
January 2010, and 2.6.34 dates from May 2010.
[1] http://lists.openwall.net/linux-ext4/2010/01/04/8
The team at Taobao was using a similar vintage kernel if I recall
correctly, at least at one point in time. I'm not sure if they have
since upgraded to a newer kernel.
However, at Google, we used a huge number of patches to fix and
stablize ext4. The patches were pushed upstream over a 18 months or
so, but not all of them were backported into 2.6.34.x kernels. I
believe you will find the same story at Red Hat and at Tao Bao.
Part of that is because the stable kernel maintainers will generally
just drop a patch if it doesn't apply cleanly. In order to determine
which patches are applicable, and to adopt and backport patches, you
really will need one or more ext4 developers on staff, such as Eric
Sandeen and his colleagues for Red Hat, or me and my colleages for
Google, or Tao Ma and his team at Taobao.
Whether or not it's good enough for your streaming media application
is a different question. That's a very restricted use case, and it
might be good enough. You should test it and see for yourself.
Regards,
- Ted
next prev parent reply other threads:[~2013-02-02 3:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-02 2:30 Help to know the stable ver of ext4 for commercial app Wuqixuan
2013-02-02 3:23 ` Theodore Ts'o [this message]
2013-02-02 7:20 ` Wuqixuan
2013-02-02 18:08 ` Andreas Dilger
[not found] ` <BB7C62C2B0732E4DA93834A501E8464544E62883@SZXEML519-MBS.china.huawei.com>
2013-02-03 12:55 ` 答复: " Theodore Ts'o
[not found] ` <BB7C62C2B0732E4DA93834A501E8464544E628B1@SZXEML519-MBS.china.huawei.com>
2013-02-04 17:52 ` qixuan wu
2013-02-05 1:17 ` Li Zefan
2013-02-05 15:20 ` Eric Sandeen
2013-02-02 22:43 ` Theodore Ts'o
[not found] ` <BB7C62C2B0732E4DA93834A501E8464544E628A6@SZXEML519-MBS.china.huawei.com>
2013-02-03 17:39 ` qixuan wu
2013-02-03 22:52 ` Theodore Ts'o
2013-02-04 17:53 ` qixuan wu
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=20130202032307.GA16364@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@sun.com \
--cc=linux-ext4@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=tm@tao.ma \
--cc=wuqixuan@huawei.com \
--cc=xiaoqiangnk@gmail.com \
/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).