On 2013/2/5 1:52, qixuan wu wrote: > On Sun, Feb 3, 2013 at 8:43 PM, Wuqixuan <wuqixuan@xxxxxxxxxx> wrote: > >> On 2013-02-02, at 0:20, Wuqixuan <wuqixuan@xxxxxxxxxx> wrote: >>> >>> Thanks a lot for your information. Has some doubt below. >>> >>>> 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. >> >> If you are looking at stability for a commercial application, I think you would be best off to choose something like RHEL6 2.6.32 which has back ported all of these patches for ext4 already and will continue to get fixes for years to come. >> >> Next best would be to pick something like FC18 3.8(?), which also has the needed patches, but will not be supported for as long a time. This is definitely still better than picking the vanilla kernel of the same version. >> >> That way, you can focus on your application, and not on becoming a kernel maintainer... > > Thanks andreas, will check the RHEL6 2.6.32 ext4 and compare with > Windriver 4.3 (2.6.34.10) which we are ready to use. Do you have any > idea of ext4 of Windriver 4.3 (2.6.34.10) ? > I think you should stop asking about Windriver as you were already told so twice. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
