From: Stan Hoeppner <stan@hardwarefreak.com>
To: xfs@oss.sgi.com
Subject: XFS binary code size
Date: Mon, 26 Sep 2011 18:12:45 -0500 [thread overview]
Message-ID: <4E8106ED.9040909@hardwarefreak.com> (raw)
I'm curious about the footprint of the XFS binary code, specifically for
32 bit systems, but knowing the 64 bit case would be educational as well
for comparison. I don't use kernel modules or I'd already have a rough
answer. My last build was 2.6.38.6 but I'm sure the size hasn't changed
much in more recent kernels. My XFS build options were:
$ grep -i xfs .config
CONFIG_XFS_FS=y
# CONFIG_XFS_QUOTA is not set
# CONFIG_XFS_POSIX_ACL is not set
# CONFIG_XFS_RT is not set
My resulting kernel image is:
$ la /boot/vmlinuz-2.6.38.6
-rw-r--r-- 1 root root 1.6M May 17 23:55 vmlinuz-2.6.38.6
How much of that 1.6MB is XFS? Also, what is the size of the hot path
code that we want to stay in L1 during heavy IO?
--
Stan
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next reply other threads:[~2011-09-26 23:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 23:12 Stan Hoeppner [this message]
2011-09-27 1:47 ` XFS binary code size Dave Chinner
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=4E8106ED.9040909@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--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