From owner-svn-src-stable@freebsd.org Mon Oct 10 18:19:40 2016 Return-Path: Delivered-To: svn-src-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4C64FC0C529; Mon, 10 Oct 2016 18:19:40 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0B95AE1D; Mon, 10 Oct 2016 18:19:40 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1btfAn-000I8o-TI; Mon, 10 Oct 2016 21:19:37 +0300 Date: Mon, 10 Oct 2016 21:19:37 +0300 From: Slawa Olhovchenkov To: Navdeep Parhar Cc: John Baldwin , src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-stable@freebsd.org, svn-src-stable-11@freebsd.org Subject: Re: svn commit: r306661 - in stable/11/sys/dev/cxgbe: . tom Message-ID: <20161010181937.GY54003@zxy.spb.ru> References: <201610032315.u93NFiHE057529@repo.freebsd.org> <20161010110901.GH6177@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: svn-src-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SVN commit messages for all the -stable branches of the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2016 18:19:40 -0000 On Mon, Oct 10, 2016 at 11:13:20AM -0700, Navdeep Parhar wrote: > On 10/10/2016 04:09, Slawa Olhovchenkov wrote: > > On Mon, Oct 03, 2016 at 11:15:44PM +0000, John Baldwin wrote: > > > >> Author: jhb > >> Date: Mon Oct 3 23:15:44 2016 > >> New Revision: 306661 > >> URL: https://svnweb.freebsd.org/changeset/base/306661 > >> > >> Log: > >> MFC 303405: Add support for zero-copy aio_write() on TOE sockets. > >> > >> ... > > > > Do you have any public available application patches for support this? > > netperf has support for AIO in its trunk/ branch and I assume it will be > part of the next netperf release. > > > May be nginx? > > > > You don't need any patches if nginx supports AIO (aio_write(2) on the > socket) already. There's usually a knob in such applications that lets No, nginx currently don't supports AIO on the socket. > you select the method it uses to transmit data. That's probably the > best place to start looking. > > Regards, > Navdeep