mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kuznet@ms2.inr.ac.ru
To: chris@scary.beasts.org (Chris Evans)
Cc: linux-kernel@vger.kernel.org, davem@redhat.com
Subject: Re: SO_SNDTIMEO: 2.4 kernel bugs
Date: Sun, 18 Feb 2001 22:48:00 +0300 (MSK)	[thread overview]
Message-ID: <200102181948.WAA27407@ms2.inr.ac.ru> (raw)
In-Reply-To: <Pine.LNX.4.30.0102181935130.31140-100000@ferret.lmh.ox.ac.uk> from "Chris Evans" at Feb 18, 1 07:37:33 pm

Hello!

> .. unless that page was partially written, in which case a short write
> count is returned (rather than a timeout error), and the loop goes around
> again.

sendfile() does not return on partial write and tries to push more
until error. On fast link it most likely succeeds, so that it is unkillable
even with SIGKILL.


> Which is good, because SO_SNDTIMEO is an inactivity monitor.

Then why did you blame? 8)8)

I do not think so. It is rather scheduling breaker. If connection
is idle 99% of time, but wakes each sndtimeo-1usec, it must yuild,
otherwise thread is lost for production.

Alexey

  reply	other threads:[~2001-02-18 19:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-17  1:35 Chris Evans
2001-02-17 20:29 ` kuznet
2001-02-17 21:56   ` Chris Evans
2001-02-17 22:46   ` Chris Evans
2001-02-18 17:24     ` kuznet
2001-02-18 19:25       ` Chris Evans
2001-02-18 19:33         ` kuznet
2001-02-18 19:37           ` Chris Evans
2001-02-18 19:48             ` kuznet [this message]
2001-02-19  1:04       ` Chris Evans
2001-02-19  1:43         ` sendfile() breakage was " Chris Evans
2001-02-19 18:03         ` kuznet
2001-02-19 21:56           ` Chris Evans
2001-02-20 15:09             ` David Woodhouse
2001-02-18  1:50   ` Chris Evans

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=200102181948.WAA27407@ms2.inr.ac.ru \
    --to=kuznet@ms2.inr.ac.ru \
    --cc=chris@scary.beasts.org \
    --cc=davem@redhat.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

all inboxes | Powered by JetHome®