The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Gianni Tedesco <gianni@ecsc.co.uk>
To: David Schwartz <davids@webmaster.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: TCP memory pressure question
Date: 22 Nov 2002 12:06:29 +0000	[thread overview]
Message-ID: <1037966789.6079.33.camel@lemsip> (raw)
In-Reply-To: <20021121213447.AAA4864@shell.webmaster.com@whenever>

[-- Attachment #1: Type: text/plain, Size: 567 bytes --]

On Thu, 2002-11-21 at 21:34, David Schwartz wrote:
> 	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?

from write(2) man page.

EAGAIN Non-blocking I/O has been selected using O_NONBLOCK and the write
would block.

-- 
// Gianni Tedesco (gianni at ecsc dot co dot uk)
lynx --source www.scaramanga.co.uk/gianni-at-ecsc.asc | gpg --import
8646BE7D: 6D9F 2287 870E A2C9 8F60 3A3C 91B5 7669 8646 BE7D

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2002-11-22 11:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-21 21:34 TCP memory pressure question David Schwartz
2002-11-22 12:06 ` Gianni Tedesco [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2002-11-22  1:27 Nivedita Singhvi
2002-11-22  9:18 ` Alex Riesen

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=1037966789.6079.33.camel@lemsip \
    --to=gianni@ecsc.co.uk \
    --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