From owner-freebsd-arch@FreeBSD.ORG Fri Aug 19 09:36:33 2011 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0F955106566B; Fri, 19 Aug 2011 09:36:33 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id DBE1D8FC08; Fri, 19 Aug 2011 09:36:32 +0000 (UTC) Received: from [192.168.2.124] (host81-151-180-177.range81-151.btcentralplus.com [81.151.180.177]) by cyrus.watson.org (Postfix) with ESMTPSA id D643746B06; Fri, 19 Aug 2011 05:36:31 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: "Robert N. M. Watson" In-Reply-To: <20110819090536.GA92576@zxy.spb.ru> Date: Fri, 19 Aug 2011 10:36:29 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <810527321.20110819123700@serebryakov.spb.ru> <319607032.20110819125005@serebryakov.spb.ru> <20110819090536.GA92576@zxy.spb.ru> To: Slawa Olhovchenkov X-Mailer: Apple Mail (2.1084) Cc: Lev Serebryakov , freebsd-arch@freebsd.org Subject: Re: FreeBSD problems and preliminary ways to solve X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Aug 2011 09:36:33 -0000 On 19 Aug 2011, at 10:05, Slawa Olhovchenkov wrote: >> Is the issue here that FreeBSD is dropping more packes, or just that = FreeBSD=20 >> is reporting that it drops packets? Historically, we've returned = ENOBUFS from=20 >> datagram sockets when the interface queue is overflowed, but some = other=20 >> systems (most noticeably Linux) simply return success when they drop = a packet=20 >> on an outgoing interface queue. You can debate which is the better = model, but=20 >> one impact is that sometimes people report errors on FreeBSD that = they don't=20 >> see on Linux -- when actually, the same failure is present, we just = allow the=20 >> application to learn about it. >=20 > Historically, Linux on datagram (UDP) socket allow use select, FreeBSD > -- don't allow. FreeBSD always report 'UDP socket ready to transmit'. > And after try to send packet -- 'oops, ENOBUFS'. And if you have two consumers sending UDP on Linux, they both get = unreported 50% packet loss, to my understanding? Robert=