From owner-freebsd-arch@FreeBSD.ORG  Thu May 29 08:38:22 2003
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 83D3B37B401
	for <arch@freebsd.org>; Thu, 29 May 2003 08:38:22 -0700 (PDT)
Received: from stork.mail.pas.earthlink.net (stork.mail.pas.earthlink.net
	[207.217.120.188])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1354243F75
	for <arch@freebsd.org>; Thu, 29 May 2003 08:38:22 -0700 (PDT)
	(envelope-from tlambert2@mindspring.com)
Received: from user-38lc1ds.dialup.mindspring.com ([209.86.5.188]
	helo=mindspring.com)
	by stork.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128)
	(Exim 3.33 #1)	id 19LPTp-0000YD-00; Thu, 29 May 2003 08:38:14 -0700
Message-ID: <3ED6291B.36F382F@mindspring.com>
Date: Thu, 29 May 2003 08:36:59 -0700
From: Terry Lambert <tlambert2@mindspring.com>
X-Mailer: Mozilla 4.79 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Igor Sysoev <is@rambler-co.ru>
References: <Pine.BSF.4.21.0305291153300.52120-100000@is>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a40d3be225e75d3443d62eddb25e663b4d350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
cc: arch@freebsd.org
Subject: Re: sendfile(2) SF_NOPUSH flag proposal
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussion related to FreeBSD architecture
	<freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 29 May 2003 15:38:22 -0000

Igor Sysoev wrote:
> On Wed, 28 May 2003, Terry Lambert wrote:
> > Igor Sysoev wrote:
> > > > will result in you sleeping with PRUS_MORETOCOME set, but with
> > > > no more being sent because the send buffer doesn't get emptied,
> > > > as it's waiting for more data to send.
> > >
> > > But as I understand PRUS_MORETOCOME is not set if socket is non-blocking.
> >
> > Then the bug is still not fixed by setting it, since your total
> > send size might be less than `sysctl net.inet.tcp.sendspace`.
> 
> Why ? We can reset TF_MORETOCOME if the sending is completed.

It's called a "deadly embrace" deadlock.  Look it up.

-- Terry