From: Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: top stack (l)users for 2.5.69
Date: Thu, 8 May 2003 17:10:42 +0200 [thread overview]
Message-ID: <20030508171042.V626@nightmaster.csn.tu-chemnitz.de> (raw)
In-Reply-To: <20030507133856.02748f4e.rddunlap@osdl.org>; from rddunlap@osdl.org on Wed, May 07, 2003 at 01:38:56PM -0700
On Wed, May 07, 2003 at 01:38:56PM -0700, Randy Dunlap wrote:
> I've written a few of the stack reduction patches. Lots of ioctl functions
> need work, so gcc handling it better would be good to have.
>
> I have mostly used kmalloc/kfree, but using automatic variables is certainly
> cleaner to write (code). One of the patches that I did just made each ioctl
> cmd call a separate function, and then each separate function was able to use
> automatic variables on the stack instead of kmalloc/kfree. I prefer this
> method when it's feasible (and until gcc can handle these cases).
Wouldn't be a explicit union a better solution for the
switch-statement-issue?
That way you still can use stack, are using even less of it and
have still all cases in place.
Regards
Ingo Oeser
--
Marketing ist die Kunst, Leuten Sachen zu verkaufen, die sie
nicht brauchen, mit Geld, was sie nicht haben, um Leute zu
beeindrucken, die sie nicht moegen.
next prev parent reply other threads:[~2003-05-08 16:54 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 13:20 top stack (l)users for 2.5.69 Jörn Engel
2003-05-07 13:45 ` Richard B. Johnson
2003-05-07 13:56 ` Jörn Engel
2003-05-07 14:16 ` Richard B. Johnson
2003-05-07 17:13 ` Jonathan Lundell
2003-05-07 17:40 ` Richard B. Johnson
2003-05-07 18:12 ` Roland Dreier
2003-05-07 18:28 ` Richard B. Johnson
2003-05-07 18:44 ` Timothy Miller
2003-05-07 18:46 ` Roland Dreier
2003-05-07 19:30 ` Richard B. Johnson
2003-05-07 19:42 ` Roland Dreier
2003-05-07 20:04 ` Richard B. Johnson
2003-05-07 20:23 ` Roland Dreier
2003-05-07 20:42 ` Timothy Miller
2003-05-08 9:06 ` Jörn Engel
2003-05-08 11:33 ` Richard B. Johnson
2003-05-08 12:00 ` Helge Hafting
2003-05-08 15:42 ` Timothy Miller
2003-05-09 8:57 ` Miles Bader
2003-05-09 16:50 ` Timothy Miller
2003-05-08 16:47 ` Davide Libenzi
2003-05-07 18:51 ` Davide Libenzi
2003-05-07 19:22 ` Richard B. Johnson
2003-05-07 19:31 ` Davide Libenzi
2003-05-07 19:39 ` Hua Zhong
2003-05-07 21:47 ` Martin J. Bligh
2003-05-08 10:29 ` David Howells
2003-05-07 17:55 ` Jörn Engel
2003-05-07 16:20 ` Martin J. Bligh
2003-05-07 19:01 ` Dave Hansen
2003-05-07 20:06 ` Jörn Engel
2003-05-07 20:14 ` Dave Hansen
2003-05-08 8:41 ` Jörn Engel
2003-05-08 16:51 ` Dave Hansen
2003-05-08 22:12 ` Jörn Engel
2003-05-07 21:30 ` Jesse Pollard
2003-05-07 21:54 ` Timothy Miller
2003-05-07 22:01 ` Jesse Pollard
2003-05-07 14:33 ` Torsten Landschoff
2003-05-07 14:47 ` William Lee Irwin III
2003-05-07 15:04 ` Torsten Landschoff
2003-05-07 16:01 ` William Lee Irwin III
2003-05-08 15:36 ` Ingo Oeser
2003-05-08 18:04 ` William Lee Irwin III
2003-05-07 15:23 ` Timothy Miller
2003-05-07 15:47 ` William Lee Irwin III
2003-05-07 16:49 ` Jörn Engel
2003-05-07 17:18 ` Davide Libenzi
2003-05-07 17:40 ` Jörn Engel
2003-05-07 18:35 ` Davide Libenzi
2003-05-07 19:45 ` Jörn Engel
2003-05-07 18:23 ` William Lee Irwin III
2003-05-07 17:38 ` William Lee Irwin III
2003-05-07 17:47 ` Jörn Engel
2003-05-07 14:49 ` Richard B. Johnson
2003-05-07 18:36 ` Linus Torvalds
2003-05-07 19:17 ` Jeff Garzik
2003-05-07 20:38 ` Randy.Dunlap
2003-05-07 21:27 ` Marcus Alanen
2003-05-07 21:27 ` Randy.Dunlap
2003-05-08 15:10 ` Ingo Oeser [this message]
2003-05-08 17:12 ` Randy.Dunlap
2003-05-07 19:38 Chuck Ebbert
2003-05-08 14:08 Chuck Ebbert
2003-05-08 18:04 ` Jonathan Lundell
2003-05-08 19:05 ` Timothy Miller
2003-05-08 21:00 ` Jonathan Lundell
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=20030508171042.V626@nightmaster.csn.tu-chemnitz.de \
--to=ingo.oeser@informatik.tu-chemnitz.de \
--cc=jgarzik@pobox.com \
--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;
as well as URLs for NNTP newsgroup(s).