[PATCH] Cleanup locking in sys_reboot() (was Re: [PATCH] Reduce stack usage in sys.c)

2005-04-01 Thread Yum Rayan
On Mar 31, 2005 12:29 AM, Jeff Garzik <[EMAIL PROTECTED]> wrote: > Your "cleanup lock usage" increases the number of lock_kernel() calls > quite a bit, which is not really a cleanup but simply bloat. Yes, just looking at the patch, seem to indicate so. But let's take a closer look at the original

Re: [PATCH] Reduce stack usage in sys.c

2005-03-31 Thread Jörn Engel
On Wed, 30 March 2005 23:44:38 -0800, Yum Rayan wrote: > > sys_reboot - 256 Also not part of any deep stack trace I found. Jörn -- There is no worse hell than that provided by the regrets for wasted opportunities. -- Andre-Louis Moreau in Scarabouche - To unsubscribe from this list

Re: [PATCH] Reduce stack usage in sys.c

2005-03-31 Thread Jeff Garzik
Yum Rayan wrote: Attempt to reduce stack usage in sys.c (linux-2.6.12-rc1-mm3). Stack usage was noted using checkstack.pl. Specifically Before patch sys_reboot - 256 After patch --- sys_reboot - none (register usage only) Along the way, wrap code to 80 column width and cleanup

[PATCH] Reduce stack usage in sys.c

2005-03-30 Thread Yum Rayan
Attempt to reduce stack usage in sys.c (linux-2.6.12-rc1-mm3). Stack usage was noted using checkstack.pl. Specifically Before patch sys_reboot - 256 After patch --- sys_reboot - none (register usage only) Along the way, wrap code to 80 column width and cleanup lock usage. S