<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 20, 2015 at 9:00 PM, Piotr Rybicki <span dir="ltr"><<a href="mailto:piotr.rybicki@innervision.pl" target="_blank">piotr.rybicki@innervision.pl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi All.<br>
<br>
Are there any plans for this feature?<br></blockquote><div><br></div><div>Yes, it is in the plans. All that is needed to another function in the api which lets you define the IO transport to use.</div><div>The functionality is already there, if you use gfapi with a volume which was created with only rdma as transport, it would use gfapi as of today.</div><div>For a tcp,rdma volume it would always use tcp and gfapi does not have a option of specifying to use rdma transport.</div><div><br></div><div>We should have it in 3.8 version of Gluster.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Just tested latest glusterfs (3.7.6), and it still doesn't work (as expected, since there was no info in changelog about it).<br>
<br>
Native RDMA transport should give a significant boost in performance, based on my observations in fuse mount.<br>
<br>
If that is any of help, I'm more than happy to test patches ;-)<br>
<br>
I'm using Mellanox QDR cards and ofed 3.12.<br>
<br>
Best regards<span class="HOEnZb"><font color="#888888"><br>
Piotr Rybicki<br>
_______________________________________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
</font></span></blockquote></div><br></div></div>