ext4 2.6.25 Merge Plans
Submitted by srlinuxx on Tue, 01/22/2008 - 21:23.
"The following patches have been in the -mm tree for a while, and I plan to push them to Linus when the 2.6.25 merge window opens," began Theodore Ts'o, offering the patches for review before they are merged. He explained that the patches introduce some of the final changes to the ext4 on-disk format, "ext4, shouldn't be deployed to production systems yet, although we do salute those who are willing to be guinea pigs and play with this code!" He continued:
"With this patch series, it is expected that [the] ext4 format should be settling down. We still have delayed allocation and online defrag which aren't quite ready to merge, but those shouldn't affect the on-disk format."
Also: Kernel space: a better btrfs
Cpu hypervisor, ext4, swap for applications ? Architecture ?
Obviously Andrew tries to do memory merge to fix all the bugs; but a new architecture should be proposed.
It seems that the cpu hypervisor is there for us to plan and fix all the application needs, on the fly. Until you recognized the hypervisor in each cpu design and use it to work on power and speed of your computer, you need to rethink any further kernel design.
Since, hdd will continue to service all computations of the cpu and support dram shortages, hypervisor has to command and control all cpu activities. so, file systems can not do it all. Priority has to be given to hypervisor operating system. Swap has to be devoted to applications and realtime threads. applications had to use hypervisor. Many application may merely transfer data for monitors without much computations, hypervisor then only handles security of the data transfer.
Until then, we are just blowing smoke.