On Thu, Jun 25, 2015 at 10:24:25AM +0800, Liu Bo wrote: > > I'm not sure I understand, you mean split the NOISIZE into two bits and > > use NOISIZE just for inode size change and the other one for the > > cow_file_range case? > > Yes, for now it has mixed meanings, either changing i_size or doing Cow. > But I think it'd better to leave it mixed if we document it well.
Agreed, please also comment the new fsync code that actually uses the nocow + notimestamp + noisize bits. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
