From owner-freebsd-virtualization@FreeBSD.ORG Sun Feb 8 13:46:26 2009 Return-Path: Delivered-To: freebsd-virtualization@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E56D1065696 for ; Sun, 8 Feb 2009 13:46:26 +0000 (UTC) (envelope-from ragnar@gatorhole.com) Received: from svosch.gatorhole.com (lonn.org [213.136.43.225]) by mx1.freebsd.org (Postfix) with ESMTP id 4A7828FC0A for ; Sun, 8 Feb 2009 13:46:26 +0000 (UTC) (envelope-from ragnar@gatorhole.com) Received: from 90-227-60-174-no53.tbcn.telia.com (90-227-60-174-no53.tbcn.telia.com [90.227.60.174]) (Authenticated sender: ragnar@gatorhole.com) by svosch.gatorhole.com (Postfix) with ESMTPSA id 23422BE577; Sun, 8 Feb 2009 14:50:28 +0100 (CET) Message-ID: <498EE22E.7020005@gatorhole.com> Date: Sun, 08 Feb 2009 14:46:22 +0100 From: Ragnar Lonn User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: ticso@cicely.de References: <498DF945.3000702@gatorhole.com> <498E0797.4040002@elischer.org> <498EC554.4020905@gatorhole.com> <20090208130435.GL32126@cicely7.cicely.de> In-Reply-To: <20090208130435.GL32126@cicely7.cicely.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Julian Elischer , freebsd-virtualization@freebsd.org Subject: Re: More open sockets with vimages? X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Feb 2009 13:46:27 -0000 Bernd Walter wrote: > This is simple maths: > 100k Sockets with 32k TX and 64k RX buffer take 9G Memory. > Just buffer space, not to mention socket state, ... > On i386 this is limited by kmem, which defaults to IIRC 512MB and > is limited by 32bit virtual address space on i386. > On amd64 depending on the OS version you can have a kmem of slighty > less than 2G max or several GB. > Nevertheless you are still limited with physical RAM. > Smaller buffers are possible, but usually people want larger buffers > to keep up with recent line speeds. > Today buffer sizes can be dynamic - don't know the exact details, but > you should keep in mind that 32k/96k is already quite small for > many purposes. > But physical memory is cheap, and most low-end machines can have 16G or more today. Is it just a matter of having enough RAM and a 64-bit OS then? How much is "several GB [kmem]" that you mention above? /Ragnar