Re: [PATCH v1 0/5] Allocate cache entries from memory pool
- From
Stefan Beller <sbeller@google.com>
- Date
- Apr 20, 2018, 17:49 UTC
- Message-ID
- <CAGZ79kbOQLkNZxHbR0bDwVHbT0x47v8qp81E2WFm72HdZJ4ZRA@mail.gmail.com>
- In-Reply-To
- <xmqqwox5i0f7.fsf@gitster-ct.c.googlers.com>
Show 6 quoted lines
>> base-commit: cafaccae98f749ebf33495aec42ea25060de8682 > > I couldn't quite figure out what these five patches were based on, > even with this line. Basing on and referring to a commit that is > not part of our published history with "base-commit" is not all that > useful to others.
I'd like to second this. In the object store refactoring, I am at a point where I'd want to migrate the memory management of {object, tree, commit, tag}.c which currently is done in alloc.c to a memory pool, that has a dedicated pointer to it.
So I'd either have to refactor alloc.c to take the_repository[1] or I'd play around with the mem_pool to manage memory in the object layer. I guess this playing around can happen with what is at origin/jm/mem-pool, however the life cycle management part of the third patch[2] would allow for stopping memleaks there. So I am interested in this series as well.
[1] proof of concept in patches nearby https://public-inbox.org/git/20180206001749.218943-31-sbeller@google.com/
[2] https://public-inbox.org/git/20180417163400.3875-5-jamill@microsoft.com/
Thanks, Stefan