From owner-freebsd-net@freebsd.org Fri Jan 8 08:57:53 2016 Return-Path: Delivered-To: freebsd-net@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 A1664A676FD for ; Fri, 8 Jan 2016 08:57:53 +0000 (UTC) (envelope-from c2h@romeo.emu.st) Received: from f5.bushwire.net (f5.bushwire.net [199.48.133.46]) by mx1.freebsd.org (Postfix) with ESMTP id 7F32918EA for ; Fri, 8 Jan 2016 08:57:53 +0000 (UTC) (envelope-from c2h@romeo.emu.st) Received: by f5.bushwire.net (Postfix, from userid 1001) id 866B0AC909; Fri, 8 Jan 2016 00:57:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/simple; d=emu.st; s=2015; t=1452243471; bh=EsV84HV9BBAx2v/U1+zvTRabXSk=; h=Comments:Received:Date:Message-ID:From:To:Subject:References: MIME-Version:Content-Type:Content-Disposition:In-Reply-To; b=T/hqlbr5Kp/v8dfA2A9+cvnkmgY2WvvlAE2OlgFyWyDVEOeTJh5at4/GDS0UtEe6N oBCckWq9tbfuyqQVgl8oea5hsVXgQTm2XZaPG58MW13xqVETdeysiKNsp44IkzGP4L tNI7XzGuCvOwarN1dbGtwyEm6UGBP1uPIbYADlms=ADlms= Comments: QMDA 0.3 Received: (qmail 10133 invoked by uid 1001); 8 Jan 2016 08:57:51 -0000 Date: 8 Jan 2016 08:57:51 +0000 Message-ID: <20160108085751.10132.qmail@f5-external.bushwire.net> From: "Mark Delany" To: freebsd-net@freebsd.org Subject: Re: Does FreeBSD have sendmmsg or recvmmsg system calls? References: <20160104210741.32812.qmail@f5-external.bushwire.net> <20160107161213.GZ3625@kib.kiev.ua> <20160107192840.GF3625@kib.kiev.ua> <20160108172323.W1815@besplex.bde.org> <20160108075815.3243.qmail@f5-external.bushwire.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Jan 2016 08:57:53 -0000 On 08Jan16, Adrian Chadd allegedly wrote: > On 7 January 2016 at 23:58, Mark Delany wrote: > I'm there, on 16 threads. That's intriquing. On CURRENT? You must be doing smarter than 16 * recvmsg() or 16 * select(). What's the thread structure? > I'd rather we do it on two or three, as a lot of time is wasted in > producer/consumer locking. but yeah, 500k tx/rx should be doable per > CPU with only locking changes. Locking changes in user space or kernel space? Mark.