From: Krzysztof Halasa <khc@pm.waw.pl>
To: Chris Mason <mason@suse.com>
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: [PATCH] multi item packed files
Date: Fri, 22 Apr 2005 11:48:48 +0200 [thread overview]
Message-ID: <m3r7h3rvjz.fsf@defiant.localdomain> (raw)
In-Reply-To: <200504211622.48065.mason@suse.com> (Chris Mason's message of "Thu, 21 Apr 2005 16:22:46 -0400")
Chris Mason <mason@suse.com> writes:
> Shrug, we shouldn't need help from the kernel for something like this.
> git as
> a database hits worst case scenarios for almost every FS.
Not sure.
> 1) subdirectories with lots of files
Correct. But git doesn't search dirs so it's not that bad.
> 2) wasted space for tiny files
... depends on block size. With 2 KB:
defiant:~$ du -s /pub/mirror/linux-2.6.git
88366 /pub/mirror/linux-2.6.git
defiant:~$ du -s --apparent-size /pub/mirror/linux-2.6.git
63400 /pub/mirror/linux-2.6.git
Not bad, is it?
> 3) files that are likely to be accessed together spread across the whole disk
... across the whole filesystem.
Well, probably it isn't best to have git and .iso archives on the same
filesystem.
--
Krzysztof Halasa
prev parent reply other threads:[~2005-04-22 9:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 15:13 [PATCH] multi item packed files Chris Mason
2005-04-21 15:41 ` Linus Torvalds
2005-04-21 16:23 ` Chris Mason
2005-04-21 19:28 ` Krzysztof Halasa
2005-04-21 20:07 ` Linus Torvalds
2005-04-22 9:40 ` Krzysztof Halasa
2005-04-22 18:12 ` Martin Uecker
2005-04-21 20:22 ` Chris Mason
2005-04-21 22:47 ` Linus Torvalds
2005-04-22 0:16 ` Chris Mason
2005-04-22 16:22 ` Linus Torvalds
2005-04-22 18:58 ` Chris Mason
2005-04-22 19:43 ` Linus Torvalds
2005-04-22 20:32 ` Chris Mason
2005-04-22 23:55 ` Chris Mason
2005-04-25 22:20 ` Chris Mason
2005-04-22 9:48 ` Krzysztof Halasa [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3r7h3rvjz.fsf@defiant.localdomain \
--to=khc@pm.waw.pl \
--cc=git@vger.kernel.org \
--cc=mason@suse.com \
--cc=torvalds@osdl.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