Announcement

Collapse
No announcement yet.

Google Android Gingerbread Is Using EXT4

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Google Android Gingerbread Is Using EXT4

    Phoronix: Google Android Gingerbread Is Using EXT4

    Earlier this year Google announced they would be switching to the EXT4 file-system on their Linux servers (previously they were still using the mature EXT2) and at the same time it was made available they had hired Ted Ts'o, the lead developer of this file-system currently in use by a majority of the new Linux desktop distributions. Google's continuing to love the EXT4 file-system and now with their new Android 2.3 "Gingerbread" operating system for smart-phones and other mobile devices, they are switching to EXT4 there too...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Unfortunately a new file system won't do much for certian models such as the Samsung Galaxy S. A couple of our sales reps have them and are on their 4th and 5th replacements despite only having them for only 4 months (memory going bad). (It also happens to be the only android offering the local telco offers).

    Comment


    • #3
      Smart phones typically use raw flash devices, which means that the filesystem must implement wear levelling. Ext4 to my knowledge does not implement any wear levelling, so this change will kill smart phones very quickly. It is great for fans of forced obsolescence, but it seems a little evil to me.

      Comment


      • #4
        Originally posted by Shining Arcanine View Post
        Smart phones typically use raw flash devices, which means that the filesystem must implement wear levelling. Ext4 to my knowledge does not implement any wear levelling, so this change will kill smart phones very quickly. It is great for fans of forced obsolescence, but it seems a little evil to me.
        Wear leveling really shouldn't be a concern on a smartphone. The amount of read/writes with a typical user would be at pretty much the lowest end of the scale. The average USB key would go through many more read/write cycles and seem to be more reliable. It's not like your going to use a smart phone for daily backups.

        Comment


        • #5
          You could also implement wear-leveling at the block level, though. Perhaps they do that?

          Comment


          • #6
            Uh. Something is not quite right here. EXT4 and NAND flash devices just are not compatible. Scary that such a prominent developer as Ted can miss this point.

            Comment


            • #7
              I suspect that this will only be applied to devices with an ftl device onboard. I just don't see how you could apply ext4 (which is for block devices) to NAND flash (which is a mtd device).

              However recent HTC devices have been using emmc for their storage and ext4 would work there as emmc has the flash controller and nand embedded directly in the same ic.

              I do wonder what performance benefits one would get using ext4 besides having extents.

              Comment


              • #8
                Originally posted by manninej View Post
                Uh. Something is not quite right here. EXT4 and NAND flash devices just are not compatible.
                Since when?

                Comment


                • #9
                  Most new phones are using block level storage these days. Wear leveling is implemented in hardware. For example, the Nexus S uses an internal SD card for storage. Ext4 is perfectly suited for this as many Galaxy S users can attest.

                  Comment


                  • #10
                    Originally posted by deanjo View Post
                    Since when?
                    I should have clarified that raw NAND devices are not compatible. If the things are as Dalingrin says then it can be used.

                    Comment

                    Working...
                    X