From owner-freebsd-current@FreeBSD.ORG Sat Mar 29 22:54:55 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1FD88366; Sat, 29 Mar 2014 22:54:55 +0000 (UTC) Received: from mx1.fisglobal.com (mx1.fisglobal.com [199.200.24.190]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mx1.fisglobal.com", Issuer "VeriSign Class 3 Secure Server CA - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DC2D25F4; Sat, 29 Mar 2014 22:54:54 +0000 (UTC) Received: from smarthost.fisglobal.com ([10.132.206.191]) by ltcfislmsgpa07.fnfis.com (8.14.5/8.14.5) with ESMTP id s2TMsriJ004442 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Sat, 29 Mar 2014 17:54:54 -0500 Received: from THEMADHATTER (10.242.181.54) by smarthost.fisglobal.com (10.132.206.191) with Microsoft SMTP Server id 14.3.174.1; Sat, 29 Mar 2014 17:54:52 -0500 From: Sender: Devin Teske To: "'Julian Elischer'" , "'Steve Kargl'" , "'Joe Nosay'" References: <53365D6F.5020804@allanjude.com> <20140329055249.GA69809@troutmask.apl.washington.edu> <53374C0B.1050901@freebsd.org> In-Reply-To: <53374C0B.1050901@freebsd.org> Subject: RE: A proposal Date: Sat, 29 Mar 2014 15:54:46 -0700 Message-ID: <046101cf4ba1$e2850520$a78f0f60$@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 15.0 Thread-Index: AQLZcUdq9Os/bLb66jnfwcrAJY+BOQGEohnhAllieNwCKPUcLQEe8OIFmKsxbjA= Content-Language: en-us X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87, 1.0.14, 0.0.0000 definitions=2014-03-29_02:2014-03-28,2014-03-29,1970-01-01 signatures=0 Cc: 'freebsd-current' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 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: Sat, 29 Mar 2014 22:54:55 -0000 > -----Original Message----- > From: Julian Elischer [mailto:julian@freebsd.org] > Sent: Saturday, March 29, 2014 3:41 PM > To: Steve Kargl; Joe Nosay > Cc: freebsd-current > Subject: Re: A proposal > > On 3/29/14, 4:52 PM, Steve Kargl wrote: > > On Sat, Mar 29, 2014 at 01:46:15AM -0400, Joe Nosay wrote: > >> On Sat, Mar 29, 2014 at 1:43 AM, Allan Jude > wrote: > >> > >>> On 2014-03-29 01:22, Joe Nosay wrote: > >>>> I have noticed that options VPS, VIMAGE, and MROUTING are not > >>>> standard > >>> for > >>>> the kernel with a base install. Is there any way that these can be > >>>> made a part of the normal kernel so that jail(s) would get the full > >>>> benefit without a kernel recompile? > >>>> _______________________________________________ > >>>> freebsd-current@freebsd.org mailing list > >>>> http://lists.freebsd.org/mailman/listinfo/freebsd-current > >>>> To unsubscribe, send any mail to " > >>> freebsd-current-unsubscribe@freebsd.org" > >>> VIMAGE has some problems with PF. Martin Matu ska said at > AsiaBSDCon > >>> that he had a patch that solves the issue. > >> Really, you say? That's good news. > >> So, will those options soon be standard for a first time install? > > Certainly, hope not. I don't use any of options. > funnily, the only profiling speed differences we've seen with enabling > netgraph is speedups :-) especially with comparing many sessions on one > vnet with the same number of sessions on several vnets. > > Last time I tested it, putting several services on different vimage jails and > assigning them different interfaces actually ran faster than having the same > services on the same VM (machine). I think we all owe this one gentleman a great show of gratitude for his work on netgraph (initially @ whistle) -- Devin (smiles) _____________ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.