From owner-freebsd-hackers@FreeBSD.ORG Tue Mar 5 19:21:00 2013 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 696A1A28 for ; Tue, 5 Mar 2013 19:21:00 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 4833A87B for ; Tue, 5 Mar 2013 19:21:00 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id A0B21B992; Tue, 5 Mar 2013 14:20:59 -0500 (EST) From: John Baldwin To: freebsd-hackers@freebsd.org Subject: Re: Need advice on sys5 shm and zero copy sockets Date: Tue, 5 Mar 2013 14:11:24 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201303051411.24608.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 05 Mar 2013 14:20:59 -0500 (EST) Cc: gary mazzaferro X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Mar 2013 19:21:00 -0000 On Monday, March 04, 2013 1:24:08 pm gary mazzaferro wrote: > Hi, > > Thanks for all the help.. Looks like I'll move forward with > recommending linux as a base for our new cloud execution containers. > > Personally, I thought freebsd would be a technically superior and > longer term solution for scientific grid and cloud, but if I can't get > support on best architectural practices. I'll need to move to > something I that will be supported during eval, design and prototyping > processes. There is not anything in stock FreeBSD that currently does zero-copy sockets for TCP. You could add such a thing, but you would have to implement your own. :( Some of the building blocks are in place. For example, you can create POSIX shared memory objects via shm_open() (and FreeBSD has an extension where a path of SHM_ANON creates anonymous, unnamed objects) and pass that fd into the kernel where an ioctl handler can map it into KVA using shm_map() and shm_unmap(). You'd have to change TCP to do something useful with this buffer however. -- John Baldwin