OGAWA Hirofumi <[email protected]> writes: > And blockread() of logmap never be used, we can get it via blockdev > (volume map later), I think it is more clean/efficient way than reading > logs via logmap. Because if we read the logs via logmap, it would have > data alias issue.
And if we make logmap write-only, it would become same with delalloc ->i_apos like file/directory inode without current !btree->depth hack in tux3_get_block(). So, I hope we don't need to add logmap specific code to handle page cache. (Or we can just use page cache arrary for logmap) Thanks. -- OGAWA Hirofumi <[email protected]> _______________________________________________ Tux3 mailing list [email protected] http://mailman.tux3.org/cgi-bin/mailman/listinfo/tux3
