From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: top Stack (l)users for 2.5.65
Date: Tue, 18 Mar 2003 17:24:25 +0100 [thread overview]
Message-ID: <20030318162425.GA10424@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0303171429040.2827-100000@penguin.transmeta.com>
32 functions using >=1k of kernel stack on i386
The list is _much_ shorter than the 2.5.64 one. But I don't know how
to interpret that yet.
oldconfig created about the same amount of work as allyesconfig and
hand-pruning of breaking drivers. The resulting .config might have
changed a lot, enough to account for 19 lost functions.
0xc01b6994 presto_get_fileid: sub $0x1164,%esp
0xc01b5634 presto_copy_kml_tail: sub $0x1018,%esp
0xc06b2704 i2o_proc_read_ddm_table: sub $0xb48,%esp
0xc056daf9 v4l_compat_translate_ioctl: sub $0x924,%esp
0xc05beed6 ide_unregister: sub $0x8a0,%esp
0xc05403d4 writerids: sub $0x820,%esp
0xc05855f4 w9966_v4l_read: sub $0x820,%esp
0xc06b53f4 i2o_proc_read_lan_alt_addr: sub $0x81c,%esp
0xc06b4c74 i2o_proc_read_lan_mcast_addr: sub $0x81c,%esp
0xc0540224 readrids: sub $0x810,%esp
0xc06b2bb4 i2o_proc_read_groups: sub $0x810,%esp
0xc0105409 huft_build: sub $0x598,%esp
0xc0106e59 huft_build: sub $0x598,%esp
0xc023e794 dohash: sub $0x580,%esp
0xc0438ad4 ida_ioctl: sub $0x53c,%esp
0xc0107bd4 inflate_dynamic: sub $0x52c,%esp
0xc0106104 inflate_dynamic: sub $0x51c,%esp
0xc08eb604 device_new_if: sub $0x518,%esp
0xc01ad654 presto_ioctl: sub $0x4fc,%esp
0xc05ced04 ide_config: sub $0x494,%esp
0xc0107a67 inflate_fixed: sub $0x490,%esp
0xc0105f97 inflate_fixed: sub $0x490,%esp
0xc08e7bf9 br_ioctl_device: sub $0x490,%esp
0xc0425034 parport_config: sub $0x47c,%esp
0xc07c6d04 ixj_config: sub $0x478,%esp
0xc0333b66 sha512_transform: sub $0x440,%esp
0xc09326e4 gss_pipe_downcall: sub $0x43c,%esp
0xc02a8c74 ciGetLeafPrefixKey: sub $0x41c,%esp
0xc064a804 aic7xxx_detect: sub $0x404,%esp
0xc050a998 hex_dump: sub $0x400,%esp
0xc0323942 befs_warning: sub $0x400,%esp
0xc03238f2 befs_error: sub $0x400,%esp
Jörn
--
Courage is not the absence of fear, but rather the judgement that
something else is more important than fear.
-- Ambrose Redmoon
prev parent reply other threads:[~2003-03-18 16:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-17 22:31 Linux 2.5.65 Linus Torvalds
2003-03-18 0:53 ` John Cherry
2003-03-18 5:22 ` CaT
2003-03-18 8:15 ` Christoph Hellwig
2003-03-18 9:12 ` CaT
2003-03-18 10:08 ` Roman Zippel
2003-03-18 10:35 ` CaT
2003-03-18 10:43 ` Roman Zippel
2003-03-18 10:48 ` John Bradford
2003-03-18 15:16 ` Linus Torvalds
2003-03-18 15:33 ` CaT
2003-03-18 12:45 ` Remaining occurances of DEVFS_FL_AUTO_DEVNUM in 2.5.65 Adrian Bunk
2003-03-18 15:40 ` Christoph Hellwig
2003-03-18 16:04 ` Christoph Hellwig
2003-03-18 16:24 ` Jörn Engel [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=20030318162425.GA10424@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®