<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 21, 2017 at 11:43 AM, Raghavendra G <span dir="ltr"><<a href="mailto:raghavendra@gluster.com" target="_blank">raghavendra@gluster.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">Summing up various discussions I had on this,<div><br></div><div>1. Current ping frame work should measure just the responsiveness of network and rpc layer. This means poller threads shouldn't be winding the individual fops at all (as it might add delay in reading the ping requests). Instead, they can queue the requests to a common work queue and other threads should pick up the requests.</div></div></blockquote><div><br></div><div>Patch can be found at:</div><div><a href="https://review.gluster.org/17105">https://review.gluster.org/17105</a><br></div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">4. We've fixed some lock contention issues on the brick stack due to high latency on backend fs. However, this is on-going work as contentions can be found in various codepaths (mem-pool etc).<br></div></blockquote><div><br></div><div>These patches were contributed by "Krutika Dhananjay" <<a href="http://kdhananj.at.redhat.com">kdhananj.at.redhat.com</a>>.</div><div><a href="https://review.gluster.org/16869">https://review.gluster.org/16869</a></div><div><a href="https://review.gluster.org/16785">https://review.gluster.org/16785</a></div><div><a href="https://review.gluster.org/16462">https://review.gluster.org/16462</a></div><div><br></div><div>Thanks Krutika for all those patches :).</div><div><br></div><div>regards,</div><div>Raghavendra</div></div>
</div></div>