Subject: Re: Understanding the reason for placing a tcp_sock on stack in tcp network functions

From: Arnaldo Carvalho de Melo <[email-masked]>
Date: Tue, 1 Mar 2005 07:13:48 -0300

This is not the case for at least some of these functions:

[email-masked], 2005-02-22 10:48:28-08:00, [email-masked]
  [TCP]: Fix excessive stack usage resulting in OOPS with 4KSTACKS.

  Various routines were putting a full struct tcp_sock on
  the local stack.  What they really wanted was a subset
  of this information when doing TCP options processing
  when we only have a mini-socket (for example in SYN-RECVD
  and TIME_WAIT states).

  Therefore pull out the needed information into a sub-struct
  and use that in the TCP options processing routines.

  Signed-off-by: Arnaldo Carvalho de Melo <[email-masked]>
  Signed-off-by: David S. Miller <[email-masked]>

On Mon, 28 Feb 2005 19:51:17 -0500, Stephen Torri <[email-masked]> wrote:
> I am trying to help out reducing the stack size of functions in the
> kernel. The function names and values below, with comments and
> questions, was obtained of the linux-2.6 kernel kept at bkbits.net when
> I did 'make checkstack'.