From: Yuxuan Shui <yshuiv7@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: "Vicent Martí" <tanoku@gmail.com>
Subject: Re: GSoC proposal: port pack bitmap support to libgit2.
Date: Thu, 20 Mar 2014 21:38:28 +0800 [thread overview]
Message-ID: <CAGqt0zwp2a6wrzLY0KOmH1zd0Bj5wmwvyBjy0j1JDjm3X4cSQg@mail.gmail.com> (raw)
In-Reply-To: <20140314043404.GD31906@sigill.intra.peff.net>
Hi,
Sorry for this late reply, I was busy for past few days.
On Fri, Mar 14, 2014 at 12:34 PM, Jeff King <peff@peff.net> wrote:
> On Wed, Mar 12, 2014 at 04:19:23PM +0800, Yuxuan Shui wrote:
>
>> I'm Yuxuan Shui, a undergraduate student from China. I'm applying for
>> GSoC 2014, and here is my proposal:
>>
>> I found this idea on the ideas page, and did some research about it.
>> The pack bitmap patchset add a new .bitmap file for every pack file
>> which contains the reachability information of selected commits. This
>> information is used to speed up git fetching and cloning, and produce
>> a very convincing results.
>>
>> The goal of my project is to port the pack bitmap implementation in
>> core git to libgit2, so users of libgit2 could benefit from this
>> optimization as well.
>>
>> Please let me know if my proposal makes sense, thanks.
>
> You'd want to flesh it out a bit more to show how you're thinking about
> tackling the problem:
>
> - What are the areas of libgit2 that you will need to touch? Be
> specific. What's the current state of the packing code? What
> files and functions will you need to touch?
Firstly I will need to implement bitmap creation in libgit2's
git_packbuilder_* functions (probably also git_odb_write_pack), so
libgit2 could support bitmap creation. Then I will need to change
git_revwalk_* functions to make them use bitmap. Since the operations
that can benefit from bitmap is, if my understanding is correct, all
using the git_revwalk_* functions, having bitmap support in revwalk
functions should be enough.
Files I need to touch probably are: revwalk.c pack-objects.c
If I need to change the API of packbuilder or revwalk functions I will
have to change the callers as well: push.c fetch.c and
transport/smart_protocol.c
I haven't read all the code to put together a list of functions I need
to change, but I think the list will be long.
>
> - What are the challenges you expect to encounter in porting the code?
The architecture differences between git and libgit2 will probably be
a challenge.
>
> - Can you give a detailed schedule of the summer's work? What will you
> work on in each week? What milestones do you expect to hit, and
> when?
I don't really have a plan, but I'll try to provide a rough schedule.
I'll read the code and try to understand the code, to the point where
I can start to add new code. This will probably take a week. For next
three or four weeks I should be implementing bitmap creation in
packbuilder. Then for the rest of time I will be optimizing revwalk
using bitmap.
>
> -Peff
--
Regards
Yuxuan Shui
prev parent reply other threads:[~2014-03-20 13:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 8:19 GSoC proposal: port pack bitmap support to libgit2 Yuxuan Shui
2014-03-13 17:20 ` Yuxuan Shui
2014-03-14 4:34 ` Jeff King
2014-03-20 13:38 ` Yuxuan Shui [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGqt0zwp2a6wrzLY0KOmH1zd0Bj5wmwvyBjy0j1JDjm3X4cSQg@mail.gmail.com \
--to=yshuiv7@gmail.com \
--cc=git@vger.kernel.org \
--cc=tanoku@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).