lkml.org 
[lkml]   [1999]   [Mar]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: tracing a kernel stack corruption

On Tue, 23 Mar 1999 getienne@globalserve.net wrote:

> 1. a function call a function which call another function and so on. how
> can we be sure not to go beyond 7k ? there is a automatic detection of
> this, a log/oops or other ?

the best solution is to avoid recursion. If this cannot be done then a
recursion limit has to be used.

> 2. why only 7k when a typical kernel uses 2meg ?

7k per process. With every 4k increase we get ~0.5M more wasted RAM on a
typical system.

-- mingo


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:50    [W:0.019 / U:1.768 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site