On 08/12/2012 09:30 PM, Boaz Harrosh wrote: > So for objects the wasting factor is the actual i_size extending as a cause > of layout_get, and not the number of pages served. So for us the gain is if > client, that has a much newer information about i_size, sends it on first > layout_get. Though extending file size only once on first layout_get and > not on every layout_get. > I want to clarify here. The i_size does not and must not grow as part of a layout_get. Only a layout_commit might extend i_size. the "file-size" I meant above is the current maximum size that can be described by the inode's layout device-map. The device map does grow on layout_get both for objects, as well as for example a CEPH cluster. If we send i_size from client then we only need extend device-map once during the complete writeout. (If need extending) Thanks Boaz -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
