From: Nivedita Singhvi <niv@us.ibm.com>
To: davids@webmaster.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: TCP memory pressure question
Date: Thu, 21 Nov 2002 17:27:45 -0800 [thread overview]
Message-ID: <3DDD8811.752CA2C4@us.ibm.com> (raw)
> When a Linux machine has reached the tcp_mem limit, what will happen to
> 'write's on non-blocking sockets? Will they block until more TCP memory is
> available? Will they return an error code? ENOMEM?
>
> If it varies by kernel version, details about different versions would be
> extremely helpful. I'm most interested in late 2.4 kernels.
>
> Thanks in advance.
>
Returns EAGAIN.
Fairly static ~late 2.4.
thanks,
Nivedita
next reply other threads:[~2002-11-22 1:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-22 1:27 Nivedita Singhvi [this message]
2002-11-22 9:18 ` TCP memory pressure question Alex Riesen
-- strict thread matches above, loose matches on Subject: below --
2002-11-21 21:34 David Schwartz
2002-11-22 12:06 ` Gianni Tedesco
2002-11-22 20:28 ` David Schwartz
2002-11-23 0:06 ` Jamie Lokier
2002-11-23 0:28 ` David Schwartz
2002-11-23 22:34 ` Folkert van Heusden
2002-11-23 22:54 ` David Schwartz
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=3DDD8811.752CA2C4@us.ibm.com \
--to=niv@us.ibm.com \
--cc=davids@webmaster.com \
--cc=linux-kernel@vger.kernel.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