On 06/11/2012 06:41 PM, Adamson, Andy wrote: > On Jun 11, 2012, at 10:51 AM, Boaz Harrosh wrote: >> I'm not sure I understood what you meant. >> >> In the "normal behavior" we don't send a LAYOUTRETURN at all >> in the forgetful model. Which proved beneficiary in the light >> of concurrent GETs vs RETURNs. >> >> I thought we are only taking about the error case. Do you >> mean there is a 3rd case? please explain. > > The normal case of calling LAYOUTRETURN on evict inode. > evict LAYOUTRETURN is mute because evict() means inode has no more references, which specifically means no more layout_segments which hold a reference on the inode. The interesting part is the error-handling case, on one of the layout_segments. What are we aloud to do after we send the LAYOUTRETURN to MDS. It's what I'm talking about, and is a part of of the general error-reporting in 4.2 to come. Boaz > -->Andy > >> >> 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
