From owner-freebsd-arch@FreeBSD.ORG  Wed Aug 13 01:31:16 2014
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 5F3109F6;
 Wed, 13 Aug 2014 01:31:16 +0000 (UTC)
Received: from mail-oa0-x22b.google.com (mail-oa0-x22b.google.com
 [IPv6:2607:f8b0:4003:c02::22b])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 1D66123DF;
 Wed, 13 Aug 2014 01:31:16 +0000 (UTC)
Received: by mail-oa0-f43.google.com with SMTP id i7so7969466oag.2
 for <multiple recipients>; Tue, 12 Aug 2014 18:31:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=hkiTgSqRYYBbfFHp85rFYuLxqetNG+xgkIUPAASuRRA=;
 b=zOWAY9SNtOuA0Cr+8sj/VC5Cq7bKbw1+sLRPwAuvR6pzU72TQyKxElw8uthOgbzfBL
 B9Xc5QhqzTY2XMaCvrgNm5j+yk+quxwnKwkxzxaE6NaWKRfouLdE1kEt8EM1jLx/jkeo
 mS5uqshVCMI7RaBM1Wqd9SKNk9693BWXNpSNJJ+l44+Ha5Vm5du/1DEtltR52L/elHM9
 8G1sJFTLFIIIRLoQyENtNB/rjv96JE8eaB7BCLyur1vVVgDCWzWFm4eyoMstrXeRQygA
 PyFVVtozKVgRAxXWC7QZgnnW9bJ2623+pVJvkQqgVS9fbTGxJ5w1Mh3Zj7NEa51+tcUA
 Nbdg==
MIME-Version: 1.0
X-Received: by 10.182.249.52 with SMTP id yr20mr1082394obc.10.1407893475224;
 Tue, 12 Aug 2014 18:31:15 -0700 (PDT)
Received: by 10.182.98.111 with HTTP; Tue, 12 Aug 2014 18:31:15 -0700 (PDT)
In-Reply-To: <20140812233617.GA17869@dft-labs.eu>
References: <20140717235538.GA15714@dft-labs.eu>
 <20140718155959.GN93733@kib.kiev.ua>
 <20140718191928.GB7179@dft-labs.eu>
 <201408111124.52064.jhb@freebsd.org>
 <20140812233617.GA17869@dft-labs.eu>
Date: Tue, 12 Aug 2014 21:31:15 -0400
Message-ID: <CAJ5_RoADBqeYL2=XzBeZ6d5fPVqdwkOFoe==AGOZmezBTK+5mw@mail.gmail.com>
Subject: Re: current fd allocation idiom
From: Benjamin Kaduk <bjkfbsd@gmail.com>
To: Mateusz Guzik <mjguzik@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1
Cc: Konstantin Belousov <kostikbel@gmail.com>, freebsd-arch@freebsd.org
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Wed, 13 Aug 2014 01:31:16 -0000

On Tue, Aug 12, 2014 at 7:36 PM, Mateusz Guzik <mjguzik@gmail.com> wrote:

> I would expect soabort to result in a timeout/reset as opposed to regular
> connection close.
>
> Comments around soabort suggest it should not be used as a replacement
> for close, but maybe this is largely because of what the other end will
> see. That will need to be investigated.
>
>
I added some text regarding soabort to socket.9 in r266962 -- does that
help clarify the situation?

-Ben