From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net,
"Randy.Dunlap" <rddunlap@osdl.org>
Cc: Sylvain Meyer <sylvain.meyer@worldonline.fr>
Subject: Re: intelfb stack usage
Date: Sat, 18 Dec 2004 08:14:28 +0800 [thread overview]
Message-ID: <200412180814.30855.adaplas@hotpop.com> (raw)
In-Reply-To: <41C330B6.8040504@osdl.org>
On Saturday 18 December 2004 03:17, Randy.Dunlap wrote:
> In 2.6.10-rc3-bk6, intelfb_set_par() has the distinction of being
> the largest stack user as determined by 'make checkstack':
>
> objdump -d vmlinux $(find . -name '*.ko') | \
> perl /mnt/src/linux-2610-rc3-bk6/scripts/checkstack.pl i386
> 0x00001317 intelfb_set_par: 2404
>
> because it has this large struct on the stack:
> struct intelfb_hwstate hw;
> (almost 2400 bytes)
>
> Any suggestions for how to alleviate this large stack usage?
>
> From a quick look, this is called from fb_ioctl() to fb_set_var()
> to fb_set_par().
> fb_ioctl() does acquire_console_sem(), so using kmalloc()
> here would need to use GFP_ATOMIC...
> I can do that if it's desired & acceptable.
Using kmalloc() should be acceptable. I'll CC the author.
Tony
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-18 0:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-17 19:17 intelfb stack usage Randy.Dunlap
2004-12-18 0:14 ` Antonino A. Daplas [this message]
2004-12-19 16:16 ` Sylvain Meyer
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=200412180814.30855.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=rddunlap@osdl.org \
--cc=sylvain.meyer@worldonline.fr \
/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;
as well as URLs for NNTP newsgroup(s).