<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Apr 30, 2017 at 9:33 AM, Raghavendra Gowdappa <span dir="ltr"><<a href="mailto:rgowdapp@redhat.com" target="_blank">rgowdapp@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">All,<br>
<br>
Its a common perception that the resolution of a file having linkto file on the hashed-subvol requires two hops:<br>
<br>
1. client to hashed-subvol.<br>
2. client to the subvol where file actually resides.<br>
<br>
While it is true that a fresh lookup behaves this way, the other fact that get's ignored is that fresh lookups on files are almost always prevented by readdirplus. Since readdirplus picks the dentry from the subvolume where actual file (data-file) resides, the two hop cost is most likely never witnessed by the application.<br>
<br>
A word of caution is that I've not done any testing to prove this observation :).<br></blockquote><div><br></div><div>May be you should do it and send an update. That way we can use the knowledge to do something.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
regards,<br>
Raghavendra<br>
______________________________<wbr>_________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://lists.gluster.org/<wbr>mailman/listinfo/gluster-users</a><br>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Pranith<br></div></div>
</div></div>