<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>Me and Kotresh would like to present the following topic<br>
<br>
Title: The Quest for GFID to Path Conversion<br>
<br>
Developer oriented topic to come up with the design for GFID to
Path conversion effectively without adding much overhead in I/O
performance.<br>
<br>
We plan to cover the following,<br>
<br>
- Problem<br>
- Existing solutions and disadvantageous<br>
- Proposed solution<br>
- Benchmark with and without this feature<br>
- Open discussion about issues with the proposed solution<br>
<br>
<br>
</tt>
<pre class="moz-signature" cols="72">regards
Aravinda</pre>
<div class="moz-cite-prefix">On Saturday 13 August 2016 03:45 AM,
Amye Scavarda wrote:<br>
</div>
<blockquote
cite="mid:CACDUr8VKe=cCQfOA_p0fe_radNP5p9r3EMwUjeg=Z1qcBjB50Q@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Aug 12, 2016 at 12:48 PM,
Vijay Bellur <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:vbellur@redhat.com" target="_blank">vbellur@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">Hey All,<br>
<br>
Gluster Developer Summit 2016 is fast approaching [1] on
us. We are looking to have talks and discussions related
to the following themes in the summit:<br>
<br>
1. Gluster.Next - focusing on features shaping the future
of Gluster<br>
<br>
2. Experience - Description of real world experience and
feedback from:<br>
a> Devops and Users deploying
Gluster in production<br>
b> Developers integrating Gluster
with other ecosystems<br>
<br>
3. Use cases - focusing on key use cases that drive
Gluster.today and Gluster.Next<br>
<br>
4. Stability & Performance - focusing on current
improvements to reduce our technical debt backlog<br>
<br>
5. Process & infrastructure - focusing on improving
current workflow, infrastructure to make life easier for
all of us!<br>
<br>
If you have a talk/discussion proposal that can be part of
these themes, please send out your proposal(s) by replying
to this thread. Please clearly mention the theme for which
your proposal is relevant when you do so. We will be
ending the CFP by 12 midnight PDT on August 31st, 2016.<br>
<br>
If you have other topics that do not fit in the themes
listed, please feel free to propose and we might be able
to accommodate some of them as lightening talks or
something similar.<br>
<br>
Please do reach out to me or Amye if you have any
questions.<br>
<br>
Thanks!<br>
Vijay<br>
<br>
[1] <a moz-do-not-send="true"
href="https://www.gluster.org/events/summit2016/"
rel="noreferrer" target="_blank">https://www.gluster.org/events<wbr>/summit2016/</a></blockquote>
<div> </div>
</div>
<br>
Annoyingly enough, the Google Doc form won't let people
outside of the Google Apps domain view it, which is not going
to be super helpful for this. </div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">I'll go ahead and close the Google
form, send out the talks that have already been added, and
have the form link back to this mailing list post. </div>
<div class="gmail_extra">Thanks! </div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">- amye </div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">
<div><br>
</div>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">Amye Scavarda | <a moz-do-not-send="true"
href="mailto:amye@redhat.com" target="_blank">amye@redhat.com</a>
| Gluster Community Lead</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Gluster-devel mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a>
<a class="moz-txt-link-freetext" href="http://www.gluster.org/mailman/listinfo/gluster-devel">http://www.gluster.org/mailman/listinfo/gluster-devel</a></pre>
</blockquote>
<br>
</body>
</html>