From owner-freebsd-questions@FreeBSD.ORG Sun Dec 18 14:08:50 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 893CC1065670 for ; Sun, 18 Dec 2011 14:08:50 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1D8428FC16 for ; Sun, 18 Dec 2011 14:08:49 +0000 (UTC) Received: by werb13 with SMTP id b13so1566120wer.13 for ; Sun, 18 Dec 2011 06:08:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=date:from:to:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; bh=TSXzh+ckL4KTj5AG/MRqHh7uybWrvpXqUWaMiGK5Bzk=; b=HbRikkas1lF0jf4aYPhvHOkB3n1rkLhOzr0zAfcoY+8VDzxlduH+YHxspZ8A+Zmw18 U5tdFRI9CpY9VQp/fUXMWw3kxtQCfehvej9hjljCNIxCC/MupekxjobX7KObhQISuPLL vbDpNnAGBZbwaJ+tsEfKUKW50YOXvl0cd6Qms= Received: by 10.216.131.141 with SMTP id m13mr3035773wei.30.1324217329082; Sun, 18 Dec 2011 06:08:49 -0800 (PST) Received: from gumby.homeunix.com (87-194-105-247.bethere.co.uk. [87.194.105.247]) by mx.google.com with ESMTPS id gg1sm22052906wbb.17.2011.12.18.06.08.46 (version=SSLv3 cipher=OTHER); Sun, 18 Dec 2011 06:08:47 -0800 (PST) Date: Sun, 18 Dec 2011 14:08:44 +0000 From: RW To: freebsd-questions@freebsd.org Message-ID: <20111218140844.29eae281@gumby.homeunix.com> In-Reply-To: References: <20111213131547.27bda580@gumby.homeunix.com> X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.6; amd64-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Implementation details of altq hfsc scheduler in pf 4.5 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Dec 2011 14:08:50 -0000 On Thu, 15 Dec 2011 12:52:15 -0500 Maxim Khitrov wrote: > On Tue, Dec 13, 2011 at 8:15 AM, RW > wrote: > > It's about latency, realtime has priority over non-realtime. > > I sort of understand this, but I can't figure out how that would apply > to my example: > > altq on $wan hfsc bandwidth 25Mb queue {one, two} > queue one bandwidth 70% hfsc(default, realtime 20%) > queue two bandwidth 30% hfsc(realtime 60%) > > If realtime and linkshare priorities are reversed, what happens as > total bandwidth utilization approaches 100%? It would presume that each queue gets its realtime 60% and 20%, and the other 20% would be used to get the overall ratio as close as possible to 70:30, which would mean a 60:40 split. I'm not sure though, but you could test it experimentally. > >> 2. In service curve configuration (m1, d, m2), what is 'd' relative > >> to? > > > > It looks like it's a leaky-bucket algorithm. It's not really > > relative to anything except for special cases like a traffic > > step-function. > > Can you please clarify what you mean? I'm familiar with the leaky > bucket algorithm, but it still doesn't answer what triggers the switch > from m1 to m2 and whether it's a per-queue or per-connection setting. It would be a dual bucket or something equivalent. The switch would be controlled by the level in the larger bucket.