From: Jonathan Nieder <jrnieder@gmail.com>
To: David Barr <david.barr@cordelta.com>
Cc: Git List <git@vger.kernel.org>,
"Shawn O. Pearce" <spearce@spearce.org>,
Stephen Boyd <bebarino@gmail.com>
Subject: Re: [PATCH 2/2] fast-import: use struct hash_table for objects
Date: Fri, 1 Apr 2011 21:46:36 -0500 [thread overview]
Message-ID: <20110402024636.GB6039@elie> (raw)
In-Reply-To: <1301572798-9973-3-git-send-email-david.barr@cordelta.com>
David Barr wrote:
> Signed-off-by: David Barr <david.barr@cordelta.com>
Thanks, this one is even more welcome. :) Same comments as the other
patch apply. Keeping the patch in full below so others can comment.
One comment below (search for object.c to find it; sorry).
> ---
> fast-import.c | 19 ++++++++++++-------
> 1 files changed, 12 insertions(+), 7 deletions(-)
>
> diff --git a/fast-import.c b/fast-import.c
> index 0592b21..8fd8ea9 100644
> --- a/fast-import.c
> +++ b/fast-import.c
> @@ -313,7 +313,7 @@ static off_t pack_size;
> /* Table of objects we've written. */
> static unsigned int object_entry_alloc = 5000;
> static struct object_entry_pool *blocks;
> -static struct object_entry *object_table[1 << 16];
> +static struct hash_table object_table;
> static struct mark_set *marks;
> static const char *export_marks_file;
> static const char *import_marks_file;
> @@ -555,9 +555,9 @@ static struct object_entry *new_object(unsigned char *sha1)
>
> static struct object_entry *find_object(unsigned char *sha1)
> {
> - unsigned int h = sha1[0] << 8 | sha1[1];
> + unsigned int h = sha1[0] << 24 | sha1[1] << 16 | sha1[2] << 8 | sha1[3];
> struct object_entry *e;
> - for (e = object_table[h]; e; e = e->next)
> + for (e = lookup_hash(h, &object_table); e; e = e->next)
> if (!hashcmp(sha1, e->idx.sha1))
> return e;
> return NULL;
> @@ -565,8 +565,9 @@ static struct object_entry *find_object(unsigned char *sha1)
>
> static struct object_entry *insert_object(unsigned char *sha1)
> {
> - unsigned int h = sha1[0] << 8 | sha1[1];
> - struct object_entry *e = object_table[h];
> + unsigned int h = sha1[0] << 24 | sha1[1] << 16 | sha1[2] << 8 | sha1[3];
> + struct object_entry *e = lookup_hash(h, &object_table);
> + void **pos;
object.c uses memcpy for this, like so:
memcpy(&h, sha1, sizeof(unsigned int));
which strikes me as sensible (to avoid fighting with the machine about
endianness since this table is only in memory).
>
> while (e) {
> if (!hashcmp(sha1, e->idx.sha1))
> @@ -575,9 +576,13 @@ static struct object_entry *insert_object(unsigned char *sha1)
> }
>
> e = new_object(sha1);
> - e->next = object_table[h];
> + e->next = NULL;
> e->idx.offset = 0;
> - object_table[h] = e;
> + pos = insert_hash(h, e, &object_table);
> + if (pos) {
> + e->next = *pos;
> + *pos = e;
> + }
> return e;
> }
>
> --
> 1.7.3.2.846.gf4b062
>
next prev parent reply other threads:[~2011-04-02 2:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 11:59 fast-import: use struct hash_table David Barr
2011-03-31 11:59 ` [PATCH 1/2] fast-import: use struct hash_table for atom strings David Barr
2011-04-02 2:42 ` Jonathan Nieder
2011-04-02 3:33 ` Jonathan Nieder
2011-03-31 11:59 ` [PATCH 2/2] fast-import: use struct hash_table for objects David Barr
2011-04-02 2:46 ` Jonathan Nieder [this message]
2011-04-02 2:48 ` fast-import: use struct hash_table Jonathan Nieder
2012-04-11 12:11 ` [PATCH/RFC v2 0/4] " Jonathan Nieder
2012-04-11 12:12 ` [PATCH/RFC v2 0/4 resend] " Jonathan Nieder
2012-04-11 12:13 ` [PATCH 1/4] fast-import: allow object_table to grow dynamically Jonathan Nieder
2012-04-11 12:14 ` [PATCH 2/4] fast-import: allow atom_table " Jonathan Nieder
2012-04-11 12:15 ` [PATCH 3/4] fast-import: allow branch_table " Jonathan Nieder
2012-04-11 12:15 ` [PATCH 4/4] fast-import: use DIV_ROUND_UP Jonathan Nieder
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=20110402024636.GB6039@elie \
--to=jrnieder@gmail.com \
--cc=bebarino@gmail.com \
--cc=david.barr@cordelta.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
/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).