From: "Linda A. Walsh" <xfs@tlinx.org>
To: xfs-oss <xfs@oss.sgi.com>
Subject: block sizes > 4K ?? possible w/large page support?
Date: Sun, 10 Jun 2012 20:21:35 -0700 [thread overview]
Message-ID: <4FD5643F.5070801@tlinx.org> (raw)
Is this something being thought about??
More than one of my hard disks:
/boot: 130 files in 103112 4K blocks: 793.6 blks/file
/tmp: 1401 files in 746715 4K blocks: 533.4 blks/file
/var/cache: 1438 files in 87858 4K blocks: 61.5 blks/file
/backups: 713 files in 2523985177 4K blocks: 3539951.6 blks/file
/var: 9038 files in 746715 4K blocks: 83.1 blks/file
/var/cache/squid: 570 files in 90031 4K blocks: 158.4 blks/file
/Media: 51893 files in 1691400956 4K blocks: 32594.5 blks/file
/: 37312 files in 506778 4K blocks: 14.0 blks/file
/usr/share: 320805 files in 195425485 4K blocks: 609.6 blks/file
/backups/Media: 50544 files in 1642550112 4K blocks: 32497.9 blks/file
/usr: 116650 files in 1389380 4K blocks: 12.4 blks/file
/Share: 1617995 files in 305269701 4K blocks: 189.1 blks/file
/home: 5822174 files in 195412389 4K blocks: 34.0 blks/file
All but 2 could benefit from a 16K block size, and 3 of them could benefit
from a 128K block size. Wouldn't that benefit in in freeing up some space
both on disk and in memory? Just a thought.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2012-06-11 3:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 3:21 Linda A. Walsh [this message]
2012-06-11 13:13 ` block sizes > 4K ?? possible w/large page support? Stan Hoeppner
2012-06-11 13:29 ` Carlos Maiolino
2012-06-11 14:54 ` Stan Hoeppner
2012-06-11 16:21 ` Carlos Maiolino
2012-06-11 21:25 ` Stefan Ring
2012-06-11 23:56 ` Dave Chinner
2012-06-12 0:08 ` Dave Chinner
2012-06-12 2:32 ` Eric Sandeen
2012-06-12 17:37 ` Linda A. Walsh
2012-06-12 18:55 ` Eric Sandeen
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=4FD5643F.5070801@tlinx.org \
--to=xfs@tlinx.org \
--cc=xfs@oss.sgi.com \
/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