Originally posted by kreijack
View Post
Announcement
Collapse
No announcement yet.
Google Is Exploring Potentially Using Btrfs In Android
Collapse
X
-
Originally posted by PuckPoltergeist View Postdifferent tools for different jobs
I was wondering what is using crc32c enough in an embdded NAS running a ext4 mdadm raid to make sense to use space on the silicon for an accelerator. I thought mdadm would use it somehow like when scrubbing.
Or is it for sata/ethernet? I thought it was done by the sat/ethernet controllers, not on CPU.
It can't be ext4's metadata as on Kirkwoods the kernel was an ancient 2.something.
Comment
-
Originally posted by starshipeleven View PostYeah, I guessed that a checksumming algorithm would be used for that.
I was wondering what is using crc32c enough in an embdded NAS running a ext4 mdadm raid to make sense to use space on the silicon for an accelerator. I thought mdadm would use it somehow like when scrubbing.
Or is it for sata/ethernet? I thought it was done by the sat/ethernet controllers, not on CPU.
It can't be ext4's metadata as on Kirkwoods the kernel was an ancient 2.something.Built on seven generations of the industry’s first, most scalable and widely adopted data infrastructure processors, Marvell’s OCTEON® 10, OCTEON® 10 Fusion and ARMADA® platforms, include a comprehensive range of in-line hardware accelerators and are optimized for AI cloud data centers, 5G wireless infrastructure, enterprise and wireline carrier networks.
or short anwser: iSCSI
Comment
-
Originally posted by Veto View PostUhm, no! You failed to provide even a single argument why...
Ok. How about the fact that after all these years we still don't have reliable RAID?
Also, here's an extract taken from https://www.patreon.com/bcachefs- btrfs, which was supposed to be Linux's next generation COW filesystem - Linux's answer to zfs. Unfortunately, too much code was written too quickly without focusing on getting the core design correct first, and now it has too many design mistakes baked into the on disk format and an enormous, messy codebase - bigger that xfs. It's taken far too long to stabilize as well - poisoning the well for future filesystems because too many people were burned on btrfs, repeatedly (e.g. Fedora's tried to switch to btrfs multiple times and had to switch at the last minute, and server vendors who years ago hoped to one day roll out btrfs are now quietly migrating to xfs instead).
Comment
-
Originally posted by nomadewolf View Post
Do i really need to?
Ok. How about the fact that after all these years we still don't have reliable RAID?
Also, here's an extract taken from https://www.patreon.com/bcachefs- btrfs, which was supposed to be Linux's next generation COW filesystem - Linux's answer to zfs. Unfortunately, too much code was written too quickly without focusing on getting the core design correct first, and now it has too many design mistakes baked into the on disk format and an enormous, messy codebase - bigger that xfs. It's taken far too long to stabilize as well - poisoning the well for future filesystems because too many people were burned on btrfs, repeatedly (e.g. Fedora's tried to switch to btrfs multiple times and had to switch at the last minute, and server vendors who years ago hoped to one day roll out btrfs are now quietly migrating to xfs instead).
Comment
-
Originally posted by chithanh View Post
Comment
Comment