> On Sat, 23 Oct 1999 17:36:12 +0200,
> Manfred Spraul <firstname.lastname@example.org> wrote:
> >How much stack space can I use without causing a stack overflow? None of
> >these functions are recursive, and they don't call any subfunctions
> >which need more than a few bytes stack space.
> Anybody looking at stack usage might find this script useful, it can
> also be found in ftp://ftp.ocs.com.au/pub/kernel.stack.gz. It taks a
> while to run, mainly because objdump --disassemble of everything takes
> a while. Some interesting results from 2.2.23 :-
> 7c4 ncr53c8xx_detect
I haven't be teached of anything there. I know of that since it has been
introduced in the driver. The table in question is used for keeping track
of each HBA NVRAM content and is used for applying the boot order.
This has the effect to limit the number of supported HBA to 8, in order
not to eat too much kernel stack.
The sym53c8xx driver allocates dynamically 1 PAGE for the table and only
keeps track of a single NVRAM instance for the boot order. The max number
of supported HBAs is then more than 40.
By the way, the init code of the sym53c8xx driver is candidate for the
ncr53c8xx driver given some minor changes. I just haven't find time for
moving this code for the moment.
> 824 dvd_read_disckey
> 824 dvd_read_manufact
> 914 mmc_ioctl
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
Please read the FAQ at http://www.tux.org/lkml/