From owner-freebsd-current@FreeBSD.ORG Fri Jun 3 16:03:47 2011 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 47B2E106566B; Fri, 3 Jun 2011 16:03:47 +0000 (UTC) (envelope-from daniel@digsys.bg) Received: from smtp-sofia.digsys.bg (smtp-sofia.digsys.bg [193.68.3.230]) by mx1.freebsd.org (Postfix) with ESMTP id C7B828FC12; Fri, 3 Jun 2011 16:03:46 +0000 (UTC) Received: from dcave.digsys.bg (dcave.digsys.bg [192.92.129.5]) (authenticated bits=0) by smtp-sofia.digsys.bg (8.14.4/8.14.4) with ESMTP id p53FXggN079120 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 3 Jun 2011 18:33:47 +0300 (EEST) (envelope-from daniel@digsys.bg) Message-ID: <4DE8FED5.6020308@digsys.bg> Date: Fri, 03 Jun 2011 18:33:41 +0300 From: Daniel Kalchev User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.2.17) Gecko/20110519 Thunderbird/3.1.10 MIME-Version: 1.0 To: Maxim Sobolev References: <4DDD4890.70604@FreeBSD.org> <86hb8du5fo.fsf@kopusha.home.net> <4DE89AA3.908@FreeBSD.org> In-Reply-To: <4DE89AA3.908@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Mikolaj Golub , Pawel Jakub Dawidek , "current@freebsd.org" Subject: Re: Weird issue with hastd(8) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Jun 2011 16:03:47 -0000 On 03.06.11 11:26, Maxim Sobolev wrote: > On 5/29/2011 4:11 AM, Mikolaj Golub wrote: >> This might be MSG_WAITALL issue I described on net@ (look for the thread >> "recv() with MSG_WAITALL might stuck when receiving more than >> rcvbuf", and >> also kern/154504). >> >> Could you please try the patch? >> >> http://people.freebsd.org/~trociny/uipc_socket.c.patch > > Yes, installing this patch on both client and server has solved this > issue. Synchronization now goes much faster. > This patch also apparently resolved the issue I had with HAST over 10Gbit Ethernet. It should probably be committed. Daniel