From owner-freebsd-ipfw@FreeBSD.ORG Wed Nov 19 06:16:41 2014 Return-Path: Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 852354EB for ; Wed, 19 Nov 2014 06:16:41 +0000 (UTC) Received: from smtp.rlwinm.de (smtp.rlwinm.de [IPv6:2a01:4f8:201:31ef::e]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 49552115 for ; Wed, 19 Nov 2014 06:16:41 +0000 (UTC) Received: from hexe.rlwinm.de (p57A7D672.dip0.t-ipconnect.de [87.167.214.114]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.rlwinm.de (Postfix) with ESMTPSA id 09EF2C324 for ; Wed, 19 Nov 2014 07:16:37 +0100 (CET) Message-ID: <546C35C5.8010702@rlwinm.de> Date: Wed, 19 Nov 2014 07:16:37 +0100 From: Jan Bramkamp User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-ipfw@freebsd.org Subject: Re: FreeBSD max pipe size? References: <543C4825.6030901@nyi.net> In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2014 06:16:41 -0000 On 14.10.2014 00:13, Michael Sierchio wrote: > On Mon, Oct 13, 2014 at 2:46 PM, Jack Barber wrote: > >> I am trying to set up dummynet with FreeBSD 9.3 and a 10 GB Fibre over >> ethernet NIC (ix drivers). >> >> Dummynet appears to have a limit of 1.25 gigabits a second, and when I >> start setting extremely large pipe values I start running into: IIRC dummynet stores the pipe bandwidth in bits per seconds in a 32 bit integer. This limits dummynet to ca. 4.2Gb/s. I don't know if this representation is exported as part of a KBI. If it is changing it to a 64 bit integer would break the KBI and will probably require someone to push for the change in 11-CURRENT and a set of compatible APIs for 10-STABLE and maybe even 9-STABLE.