git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH/RFC v1 0/2] The ext4 filesystem and racy git

From
KBKjetil Barvik <barvik@broadpark.no>
Date
Feb 15, 2009, 19:46 UTC
Message-ID
<cover.1234720401.git.barvik@broadpark.no>

Ext4 is marked stable in Linux v2.6.28, and I have done a very simple test on one disk-partition of my slow laptop, and the numbers look very promising.

With default created ext3 disk-partition on my harddisk the 'git checkout -q my-v2.6.25/27' test takes around 20 seconds real time for the best cases. The same test run on a ext4 partition takes around 14 seconds for the best cases.

And, since ext4 supports nanosecond timestamps, when I added patch 2/2, the checkout time is much more stable and more close to 14-15 seconds most of the time.

Conclusion: for GIT on my laptop the ext4 filesystem is a speedup!
>From '/proc/mounts' here is the mount options:
  /dev/hda10 /home ext3 rw,noatime,errors=continue,data=ordered 0 0
  /dev/hda12 /opt2 ext4 rw,noatime,barrier=1,journal_async_commit,data=ordered 0 0

/dev/hda10 is formatted with default (gentoo) ext3 parameters, and the /dev/hda12 is formatted with:

  /sbin/mkfs -t ext4 -I 256 -G 64 -Oflex_bg,uninit_bg /dev/hda12
Kjetil Barvik (2):
  fix compile error when USE_NSEC is defined
  make USE_NSEC work as expected
 builtin-fetch-pack.c |    4 +-
 cache.h              |    6 ++--
 read-cache.c         |   70 ++++++++++++++++++++++++++++++++++++++++----------
 3 files changed, 61 insertions(+), 19 deletions(-)
Next: Kjetil Barvik
Message 1 of 3 in “The ext4 filesystem and racy git”
  1. 0/2 The ext4 filesystem and racy gitKjetil Barvik, Feb 15, 2009
  2. 1/2 fix compile error when USE_NSEC is definedKjetil Barvik, Feb 15, 2009
  3. 2/2 make USE_NSEC work as expectedKjetil Barvik, Feb 15, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.