Re: Developer Documentation for datastructures in gluster

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 15/07/2014, at 1:45 PM, Jeff Darcy wrote:
>>       Please respond if you guys volunteer to add documentation for any
>> of the following things that are not already taken.
> 
> I think the most important thing to describe for each of these is the
> "life cycle" rules.  When I've tried to teach people about translators,
> one of the biggest stumbling blocks has been the question of what gets
> freed after the fop, what gets freed after the callback, and what lives
> on even longer.  There are different rules for dict_t, loc_t, inode_t,
> etc.  Dict_set_*str is one of the worst offenders; even after all this
> time, I have to go back and re-check which variants do what when the
> dict itself is freed.  If the only thing that comes out of this effort
> is greater clarity regarding what should be freed when, it will be
> worth it.

+1 :)

--
GlusterFS - http://www.gluster.org

An open source, distributed file system scaling to several
petabytes, and handling thousands of clients.

My personal twitter: twitter.com/realjustinclift

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://supercolony.gluster.org/mailman/listinfo/gluster-devel




[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux