Hi,Bharata B Rao:<br> I have try your patch, but has some problem. I found that both glusterfs and qemu have a fun uuid_is_null. <br>glusterfs use contrib/uuid/isnull.c<br>qemu use block/vdi.c<br><br><br>I test the api/example, the glfsxmp.c call uuid_is_null in contrib/uuid/isnull.c<br>
but qemu/block/gluster.c finally call the uuid_is_null in vdi.c which cause vm can't boot.<br><br>I was wonder why this happen?<br><br><br>Best Regards,<br>yin.yin<br><br><div class="gmail_quote">On Fri, Aug 10, 2012 at 9:56 AM, Bharata B Rao <span dir="ltr"><<a href="mailto:bharata.rao@gmail.com" target="_blank">bharata.rao@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Fri, Aug 10, 2012 at 7:05 AM, Yin Yin <<a href="mailto:maillistofyinyin@gmail.com">maillistofyinyin@gmail.com</a>> wrote:<br>
> Bharata B Rao :<br>
> Thanks!! This is what I wanted!<br>
> I'll try your patch and make some test.<br>
> BTW: why gluster-qemu integration had so high performance than fuse<br>
> mount?<br>
<br>
</div>With no FUSE overhead, IO path becomes simpler with no back and forth<br>
transition to kernel.<br>
<br>
Regards,<br>
Bharata.<br>
</blockquote></div><br>