Date: Tue, 14 Oct 2014 11:42:25 -0400 (EDT) From: Benjamin Kaduk <kaduk@MIT.EDU> To: =?ISO-8859-15?Q?Olivier_Cochard-Labb=E9?= <olivier@cochard.me> Cc: FreeBSD Net <freebsd-net@freebsd.org>, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org>, freebsd-arch <freebsd-arch@freebsd.org> Subject: Re: Enabling VIMAGE by default for FreeBSD 11? Message-ID: <alpine.GSO.1.10.1410141141190.27826@multics.mit.edu> In-Reply-To: <CA%2Bq%2BTco_8x1YUdu65a62LTW2fKJf%2BymmierbcktEHdiKp3rcNg@mail.gmail.com> References: <CAG=rPVe_JGy%2BeUiDjHaXXi5=n2mWGOeZjHkbVeUeS_m1z1_uMg@mail.gmail.com> <BE67D12E-E8AB-401E-8B45-6BE56C1DF2FB@ipfw.ru> <CAG=rPVcWVPZoG1=c3U2ArJLEH%2BdF2kPxkfihs4J872pH9LJ0mQ@mail.gmail.com> <CA%2Bq%2BTco_8x1YUdu65a62LTW2fKJf%2BymmierbcktEHdiKp3rcNg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 14 Oct 2014, Olivier Cochard-Labbé wrote: > I can use my forwarding/firewalling 10Giga lab for testing VIMAGE impact. > Here are my ministat results (smallest packet size, value in > packet-per-second, about 2000 flows). > => I didn't see lot's of performance impact with VIMAGE option added in > kernel. Surely we would also want to test on some "low-end" networks as well ... we still have some 10/half networks here (luckily, nowhere that I frequent). -Ben From owner-freebsd-net@FreeBSD.ORG Tue Oct 14 18:17:51 2014 Return-Path: <owner-freebsd-net@FreeBSD.ORG> Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B910829E for <freebsd-net@freebsd.org>; Tue, 14 Oct 2014 18:17:51 +0000 (UTC) Received: from eastrmfepo101.cox.net (eastrmfepo101.cox.net [68.230.241.213]) by mx1.freebsd.org (Postfix) with ESMTP id 60F1FF2 for <freebsd-net@freebsd.org>; Tue, 14 Oct 2014 18:17:51 +0000 (UTC) Received: from eastrmimpo210 ([68.230.241.225]) by eastrmfepo101.cox.net (InterMail vM.8.01.05.15 201-2260-151-145-20131218) with ESMTP id <20141014181750.FTVU5255.eastrmfepo101.cox.net@eastrmimpo210> for <freebsd-net@freebsd.org>; Tue, 14 Oct 2014 14:17:50 -0400 Received: from [192.168.3.22] ([72.219.202.186]) by eastrmimpo210 with cox id 36Hp1p00K41obj4016Hp1S; Tue, 14 Oct 2014 14:17:49 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str 01.0A020205.543D68CE.0025,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.0 cv=aZC/a2Ut c=1 sm=1 a=k40gPPfQ5QH6qv5U/EJc3Q==:17 aœW_t1CCXrUA:10 aõxKl4ys9bwA:10 a=G8Uczd0VNMoA:10 a=Wajolswj7cQA:10 a=8nJEP1OIZ-IA:10 a=kviXuzpPAAAA:8 a=6I5d2MoRAAAA:8 a=M50rKQ7feiKH07HconkA:9 a=wPNLvfGTeEIA:10 a=SV7veod9ZcQA:10 a=k40gPPfQ5QH6qv5U/EJc3Q==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Message-ID: <543D68BF.40707@cox.net> Date: Tue, 14 Oct 2014 14:17:35 -0400 From: "John D. Hendrickson and Sara Darnell" <johnandsara2@cox.net> Reply-To: johnandsara2@cox.net User-Agent: Thunderbird 2.0.0.24 (X11/20100228) MIME-Version: 1.0 Subject: Re: Enabling VIMAGE by default for FreeBSD 11? References: <CAG=rPVe_JGy+eUiDjHaXXi5=n2mWGOeZjHkbVeUeS_m1z1_uMg@mail.gmail.com> <1wLg1p00d2X408g01wLiUx> In-Reply-To: <1wLg1p00d2X408g01wLiUx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-net@freebsd.org, "freebsd-virtualization@freebsd.org" <freebsd-virtualization@freebsd.org>, freebsd-arch <freebsd-arch@freebsd.org> X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>, <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>; List-Post: <mailto:freebsd-net@freebsd.org> List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>, <mailto:freebsd-net-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 14 Oct 2014 18:17:51 -0000 Alexander V. Chernikov wrote: > On 11 Oct 2014, at 21:58, Craig Rodrigues <rodrigc@FreeBSD.org> wrote: > >> Hi, >> >> What action items are left to enable VIMAGE by default for FreeBSD 11? > Are there any tests results showing performance implications on different network-related workloads? >> Not everyone uses bhyve, so VIMAGE is quite useful when using jails. >> >> -- >> Craig >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> > > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org" > i know little about chroot jails or 7 ring processor levels but let me ask rhetorically ... do you mean VIMAGE allows a jail to use an iface device for many IPs or even MAC? i thought that was already the case all cards can "listen" - it's only a headers trick per say. but do you mean a chroot can have access to an iface (which there are pkg for setting up if i remember)? but if a jail is allowed to use an iface why not allocate it - meaning: what is the purpose of middleman vimage connecting device to jail unless there is a strict filter inbetween (ie, strippign headers, or even controlling what iface/routes are alllowed)? i can't see what it's for, but much less making it mandatorily injected upon all jailsm, except maybe it may BREAK existing jails by allowing net access where there is NOT supposed to be any / assumed not to be any if they old programmers didn't want anyone compiling software who logged in: they'd insure there was no compiler. if they didn't want typing at a terminal: they'd take away the keyboard right?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.GSO.1.10.1410141141190.27826>