Re: Release 3.10 feature proposal: gfapi fix memory leak during graph switch

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

 



On 12/09/2016 08:06 AM, Rajesh Joseph wrote:
During graph switch we do not perform much cleanup operation on the
old graph, leading to memory leak.

+ Inode table of old graph needs cleanup.
       - Fix inode leaks
       - Fix forget of each xl to free inode ctx properly
+ The xl objects itself (xlator_t)
+ The mem_accnt structure in every xl object.
      - Fix all the leaks so that the ref count of mem_accnt structure is 0
+ Implement fini() in every xlator

Would need support from all other xlator owner to bring down memory
leak in each xlator.

Rajesh, I have marked this for 3.10 tentatively. As you call out a per xlator task, could you elaborate what is needed from others?

We need to possibly get ack's from the various component maintainers so that this can happen for 3.10. So if you could share a list of things that need to be done/checked for each component and drive the same, in terms of timelines, we could get this feature complete.


Thanks & Regards,
Rajesh
_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.gluster.org/mailman/listinfo/gluster-devel

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://www.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