linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* intelfb stack usage
@ 2004-12-17 19:17 Randy.Dunlap
  2004-12-18  0:14 ` Antonino A. Daplas
  0 siblings, 1 reply; 3+ messages in thread
From: Randy.Dunlap @ 2004-12-17 19:17 UTC (permalink / raw)
  To: linux-fbdev-devel

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.

-- 
~Randy


-------------------------------------------------------
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/

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: intelfb stack usage
  2004-12-17 19:17 intelfb stack usage Randy.Dunlap
@ 2004-12-18  0:14 ` Antonino A. Daplas
  2004-12-19 16:16   ` Sylvain Meyer
  0 siblings, 1 reply; 3+ messages in thread
From: Antonino A. Daplas @ 2004-12-18  0:14 UTC (permalink / raw)
  To: linux-fbdev-devel, Randy.Dunlap; +Cc: Sylvain Meyer

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/

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: intelfb stack usage
  2004-12-18  0:14 ` Antonino A. Daplas
@ 2004-12-19 16:16   ` Sylvain Meyer
  0 siblings, 0 replies; 3+ messages in thread
From: Sylvain Meyer @ 2004-12-19 16:16 UTC (permalink / raw)
  To: linux-fbdev-devel; +Cc: Randy.Dunlap

        If you can do it, thanks. I won't have any time until next year.

Sylvain

Antonino A. Daplas a écrit:

>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/
>_______________________________________________
>Linux-fbdev-devel mailing list
>Linux-fbdev-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel
>
>  
>





-------------------------------------------------------
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/

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2004-12-19 16:19 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-12-17 19:17 intelfb stack usage Randy.Dunlap
2004-12-18  0:14 ` Antonino A. Daplas
2004-12-19 16:16   ` Sylvain Meyer

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).