git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: git@vger.kernel.org
Subject: Yet another base64 patch
Date: Wed, 13 Apr 2005 21:19:48 -0700	[thread overview]
Message-ID: <425DEF64.60108@zytor.com> (raw)

I am assuming this will be the last one one way or another...

I decided that filenames/tags beginning with - was a really bad thing,
so I decided that, ugly though it might be, the best was to do a hybrid
between regular base64 (+ /) and filesystem-safe base64 (- _) and use
+ _ as the nonalpha characters needed.  I have updated the base64
patches as well as gitcvt, and also put out a flat version of gitcvt.

gitcvt also now converts the HEAD file over.  This requires pointing it
at the .dircache/.git directory instead of the objects directory inside.
  I have tested it on both the git and the kernel-test repositories.

Checking out the total kernel tree (time checkout-cache -a into an empty 
directory):

	Cache cold	Cache hot
stock	3:46.95		19.95
base64	5:56.20		23.74
flat	2:44.13		15.68

It seems that the flat format, at least on ext3 with dircache, is 
actually a major performance win, and that the second level loses quite 
a bit.

	-hpa


             reply	other threads:[~2005-04-14  4:15 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-14  4:19 H. Peter Anvin [this message]
2005-04-14  2:24 ` Yet another base64 patch Christopher Li
2005-04-14  5:36   ` H. Peter Anvin
2005-04-14  2:42     ` Christopher Li
2005-04-14  6:27       ` H. Peter Anvin
2005-04-14  6:35         ` H. Peter Anvin
2005-04-14  7:40         ` Linus Torvalds
2005-04-14 16:58           ` H. Peter Anvin
2005-04-14 17:42             ` Linus Torvalds
2005-04-14 19:11               ` bert hubert
2005-04-14 19:25                 ` H. Peter Anvin
2005-04-14 21:47                   ` bert hubert
2005-04-15  0:44                     ` Linus Torvalds
2005-04-15  1:06                       ` H. Peter Anvin
2005-04-17  4:10                         ` David Lang
2005-04-18  6:23                           ` H. Peter Anvin
2005-04-15  1:07                       ` H. Peter Anvin
2005-04-15  3:58                         ` Paul Jackson
2005-04-17  3:53                           ` David A. Wheeler
2005-04-17  4:05                             ` Paul Jackson
2005-04-17  6:38                               ` David A. Wheeler
2005-04-17  8:16                                 ` Paul Jackson
2005-04-17 17:51                                   ` David A. Wheeler
2005-04-17 18:19                                 ` Petr Baudis
2005-04-18  5:13                                   ` David A. Wheeler
2005-04-18 12:59                                     ` Kevin Smith
2005-04-18 16:42                                       ` David A. Wheeler
2005-04-17 14:30                               ` Daniel Barkalow
2005-04-17 16:29                                 ` David A. Wheeler
2005-04-14  4:25 ` H. Peter Anvin
2005-04-14  8:17 ` Linus Torvalds
2005-04-14 17:02   ` H. Peter Anvin
2005-04-15 23:55 ` Paul Dickson
2005-04-18  6:28   ` H. Peter Anvin

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=425DEF64.60108@zytor.com \
    --to=hpa@zytor.com \
    --cc=git@vger.kernel.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.
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 NNTP newsgroup(s).