From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: nathans@sgi.com, owner-xfs@oss.sgi.com
Cc: linux-kernel@vger.kernel.org
Subject: [STACK] >3k call path in xfs
Date: Wed, 9 Jun 2004 14:26:47 +0200 [thread overview]
Message-ID: <20040609122647.GF21168@wohnheim.fh-wedel.de> (raw)
xfs is quite interesting. No single function is particularly
stack-hungry, but the sheer depth of the call path adds up. Nathan,
can you see if some bytes can be saved here and there?
3k is not really bad yet, I just like to keep 1k of headroom for
surprises like an extra int foo[256] in a structure.
stackframes for call path too long (3064):
size function
144 xfs_ioctl
328 xfs_swapext
0 xfs_iaccess
16 xfs_acl_iaccess
104 xfs_attr_fetch
0 xfs_attr_node_get
28 xfs_da_node_lookup_int
68 xfs_dir2_leafn_lookup_int
0 xfs_da_read_buf
288 xfs_bmapi
52 xfs_rtpick_extent
24 xfs_trans_iget
32 xfs_iget
32 xfs_iread
72 xfs_itobp
60 xfs_imap
84 xfs_dilocate
0 xfs_inobt_lookup_le
16 xfs_inobt_increment
28 xfs_btree_readahead_core
20 xfs_btree_reada_bufl
12 pagebuf_readahead
16 pagebuf_get
0 pagebuf_iostart
0 xfs_bdstrat_cb
68 pagebuf_iorequest
0 pagebuf_iodone
0 pagebuf_iodone_work
0 pagebuf_rele
0 preempt_schedule
84 schedule
16 __put_task_struct
20 audit_free
36 audit_log_start
16 __kmalloc
0 __get_free_pages
28 __alloc_pages
284 try_to_free_pages
0 out_of_memory
0 mmput
16 exit_aio
0 __put_ioctx
16 do_munmap
0 split_vma
36 vma_adjust
0 fput
0 __fput
0 locks_remove_flock
12 panic
0 sys_sync
0 sync_inodes
308 sync_inodes_sb
0 do_writepages
128 mpage_writepages
4 write_boundary_block
0 ll_rw_block
28 submit_bh
0 bio_alloc
88 mempool_alloc
256 wakeup_bdflush
20 pdflush_operation
0 printk
16 release_console_sem
16 __wake_up
0 printk
0 vscnprintf
32 vsnprintf
112 number
Jörn
--
Ninety percent of everything is crap.
-- Sturgeon's Law
next reply other threads:[~2004-06-09 12:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-09 12:26 Jörn Engel [this message]
2004-06-09 12:54 ` Christian Borntraeger
2004-06-09 13:05 ` Jörn Engel
2004-06-09 13:10 ` Jörn Engel
2004-06-09 22:58 ` Nathan Scott
2004-06-09 15:05 ` Steve Lord
2004-06-09 16:03 ` Jörn Engel
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=20040609122647.GF21168@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nathans@sgi.com \
--cc=owner-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
all inboxes | Powered by JetHome®