From: Mitchell Blank Jr <mitch@sfgoth.com>
To: git@vger.kernel.org
Subject: [ANNOUNCE] gitfs pre-release 0.03
Date: Fri, 18 Nov 2005 04:45:32 -0800 [thread overview]
Message-ID: <20051118124532.GG87234@gaz.sfgoth.com> (raw)
I've released another pre-release of my gitfs tool tonight. The isn't a ton
of new functionality, but there has been a lot of changes:
% for dir in gitfs-0.0[123]; do echo `cat $dir/*.[ch] | wc -l` $dir; done
2228 gitfs-0.01
2334 gitfs-0.02
8276 gitfs-0.03
This is mostly because I've been working on taking it from the "proof of
concept" phase to a real filesystem. To that end:
* gitfs now does all git operations in a separate thread so accessing a
large file won't cause other filesystem operations to stall. In order
to allow multithreaded operations we no longer use the libfuse API -- we
speak the kernel/fuse API directly. This was a lot of work but it's
actually a much better fit for gitfs since it allows me to map directly
between inode #'s and the internal "gnode"'s, saving a lot of work.
Because of this you no longer need libfuse installed to use gitfs --
all you need to compile is point the Makefile at a <linux/fuse.h>
header -- the one that comes with a >=2.6.14 kernel will work fine.
However, to actually mount a fuse filesystem you'll need the "fusermount"
helper binary from fuse somewhere in $PATH
* We use the sha1_object_info() API in current versions of libgit to
avoid uncompressing blob objects if they're only being stat()'ed.
This is another big speed-up
* gitfs mounts now also create a UNIX domain socket so external clients
can make requests (for instance to optimize things like "diff")
Currently only a few simple commands are implemented, as described in
the README
* Lots of other infrastructure and data-structure work. I'm particularly
proud of my rather scary red-black tree implementation :-)
As usual tarballs are available at:
http://www.sfgoth.com/~mitch/linux/gitfs/
-Mitch
next reply other threads:[~2005-11-18 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-18 12:45 Mitchell Blank Jr [this message]
2005-11-18 14:20 ` [ANNOUNCE] gitfs pre-release 0.03 Paolo Teti
2005-11-18 20:50 ` Mitchell Blank Jr
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=20051118124532.GG87234@gaz.sfgoth.com \
--to=mitch@sfgoth.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).