From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Stephen Torri <storri@torri.org>
Cc: netdev <netdev@oss.sgi.com>
Subject: Re: Understanding the reason for placing a tcp_sock on stack in tcp network functions
Date: Tue, 1 Mar 2005 07:13:48 -0300 [thread overview]
Message-ID: <39e6f6c70503010213214101a@mail.gmail.com> (raw)
In-Reply-To: <1109638277.9693.15.camel@base.torri.org>
This is not the case for at least some of these functions:
ChangeSet@1.2035.2.55, 2005-02-22 10:48:28-08:00, acme@conectiva.com.br
[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 <acme@conectiva.com.br>
Signed-off-by: David S. Miller <davem@davemloft.net>
On Mon, 28 Feb 2005 19:51:17 -0500, Stephen Torri <storri@torri.org> 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'.
prev parent reply other threads:[~2005-03-01 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 0:51 Understanding the reason for placing a tcp_sock on stack in tcp network functions Stephen Torri
2005-03-01 10:13 ` Arnaldo Carvalho de Melo [this message]
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=39e6f6c70503010213214101a@mail.gmail.com \
--to=arnaldo.melo@gmail.com \
--cc=acme@conectiva.com.br \
--cc=netdev@oss.sgi.com \
--cc=storri@torri.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).