From: Jens Axboe <axboe@suse.de>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: joern@wohnheim.fh-wedel.de, alan@redhat.com,
linux-kernel@vger.kernel.org
Subject: Re: Top stack (l)users for 2.5.64-ac4
Date: Fri, 14 Mar 2003 19:03:27 +0100 [thread overview]
Message-ID: <20030314180327.GY791@suse.de> (raw)
In-Reply-To: <20030314095906.20a270cb.rddunlap@osdl.org>
On Fri, Mar 14 2003, Randy.Dunlap wrote:
> On Fri, 14 Mar 2003 18:41:54 +0100 Jens Axboe <axboe@suse.de> wrote:
>
> | On Fri, Mar 14 2003, Joern Engel wrote:
> | > Hi!
> | >
> | > 47 functions using >=1k of kernel stack on i386.
> | >
> | > One improvement over 2.5.64, i2o_proc_* is gone. 4 down, 47 to go. :)
> | >
> | > 0xc02063f6 presto_get_fileid: sub $0x1168,%esp
> | > 0xc0204fc6 presto_copy_kml_tail: sub $0x101c,%esp
> | > 0xc07b92c8 isp2x00_make_portdb: sub $0xc38,%esp
> | > 0xc0879c05 cdromread: sub $0xa84,%esp
> |
> | which function is this (cdromread)?
>
> must be drivers/cdrom/optcd.c::cdromread() (line 1601 in 2.5.64),
> due to
> char buf[CD_FRAMESIZE_RAWER];
> and
> #define CD_FRAMESIZE_RAWER 2646 /* The maximum possible returned bytes */
> in include/linux/cdrom.h.
Ahh, ok so a lot less interesting. Also why I didn't catch it here. I'd
be inclining to just making buf global there.
--
Jens Axboe
next prev parent reply other threads:[~2003-03-14 17:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-14 15:09 Linux 2.5.64-ac4 Alan Cox
2003-03-14 15:31 ` 2.5.64-ac4: mpparse.c doesn't compile Adrian Bunk
2003-03-14 15:32 ` Alan Cox
2003-03-14 16:53 ` Linux 2.5.64-ac4 Morten Helgesen
2003-03-14 18:34 ` Morten Helgesen
2003-03-14 17:28 ` Top stack (l)users for 2.5.64-ac4 Joern Engel
2003-03-14 17:41 ` Jens Axboe
2003-03-14 17:59 ` Randy.Dunlap
2003-03-14 18:03 ` Jens Axboe [this message]
2003-03-14 19:09 ` [patch] v4l: v4l1-compat update Gerd Knorr
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=20030314180327.GY791@suse.de \
--to=axboe@suse.de \
--cc=alan@redhat.com \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@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