From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ot0-x243.google.com (mail-ot0-x243.google.com [IPv6:2607:f8b0:4003:c0f::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id F25B73B29E for ; Wed, 25 Jan 2017 16:13:53 -0500 (EST) Received: by mail-ot0-x243.google.com with SMTP id 73so25048664otj.1 for ; Wed, 25 Jan 2017 13:13:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=I8dqvks6Qyxgi1llkllsEuYleHV6s6iFTCp4RkO0VK0=; b=XVTgsGiI87v/WVeF8a//CGEQFe4mftJtyoewL1PMwnmCyhQVfUepszxiCOQLMT/iSg 8vyTKElGl+ect78fzycpfsNgcye5XxA9wYc4caa0L33WZyVmQSNnunI9uL2zFi83Tz3k cF+6uV7nrgxnwnbD+0KoTyGwxclqfuSDTeRaiiOoAoH6KRF2mpxggoXidKnFMxX8GWZh xBMinHuvgMYpqF0gMNjvLZvQG5LSAv5DnSKz1xZ45znKWjiruk/64khprv9xakM01gIX XUzfM2wOt9U0K+pvls41vcuBkptBV0TQxtxLUm3knvVifvIeHPLhVg8rNbEsr99MnFQz K5sQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=I8dqvks6Qyxgi1llkllsEuYleHV6s6iFTCp4RkO0VK0=; b=rj6z6e2Ds5qwoe6tRPkRqeEd9Hc18p8V898L8dOlTUsIGz6Z85HybpAaopJ/9g80uT uyILBDxYswhhVBEGrqx5Lx0DLwteUC64Mw0seD76UNOoCzeHGsBxgfAiUUC1M2O3PxB5 psp+qkYJN0p+G9bluLhy4tF01Ku1EfDqaHH9NIVgHRzOp6DI4wcLudPp6pVX2z6RhfVQ uEGOpmsIAl6Jn1cFx5Um8AhpjMiOyX0oPhQzlp+nzcoGKuTBK8kjTZ/wrajbHyGTFQQN b/+bT+wD8ZYihcHb5JL/yKFuzzVegHEO2e+0FX4ivWcIE2uEAl4Yh8v46RM2WT5pDg4Z vSSQ== X-Gm-Message-State: AIkVDXJqTBFGB+WKM44czyS1a2E/Hx8Lk84ShrW8HwmtrIJBpWnoLACvanq3wZluMR0o/xuhZkHwUA13/rntZQ== X-Received: by 10.157.1.229 with SMTP id e92mr23037742ote.250.1485378833316; Wed, 25 Jan 2017 13:13:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.1.21 with HTTP; Wed, 25 Jan 2017 13:13:52 -0800 (PST) In-Reply-To: <908CA0EF-3D84-4EB4-ABD8-3042668E842E@gmail.com> References: <58D7E8D3-5661-4126-80D9-2F2D4E478B10@gmail.com> <908CA0EF-3D84-4EB4-ABD8-3042668E842E@gmail.com> From: Hans-Kristian Bakke Date: Wed, 25 Jan 2017 22:13:52 +0100 Message-ID: To: bloat@lists.bufferbloat.net Content-Type: multipart/alternative; boundary=94eb2c03c39ab780fb0546f1b5f3 Subject: Re: [Bloat] Initial tests with BBR in kernel 4.9 X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Jan 2017 21:13:54 -0000 --94eb2c03c39ab780fb0546f1b5f3 Content-Type: text/plain; charset=UTF-8 dmesg | grep HPET [ 0.000000] ACPI: HPET 0x00000000BFFE274F 000038 (v01 BOCHS BXPCHPET 00000001 BXPC 00000001) [ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000 I seem to indeed have a HPET in my VM. Does that mean that I should be able to use fq as intended or could the HPET be some kind of virtualized device? Regards, Hans-Kristian On 25 January 2017 at 22:09, Jonathan Morton wrote: > > > On 25 Jan, 2017, at 23:05, Hans-Kristian Bakke > wrote: > > > > Do I understand correctly that fq is really just hit and miss within a > VM in general then? Is there no advantage to the fair queing part even with > a low-precision clock? > > First, check using dmesg or whatever that you do, or do not, have a > working HPET within your VM. > > If this is a widespread problem, I could concoct a patch to sch_fq which > compensates for it. I already fixed the same problem when using part of > sch_fq as a basis for part of sch_cake, and demonstrated correct operation > on an old, slow PC without an HPET. > > - Jonathan Morton > > --94eb2c03c39ab780fb0546f1b5f3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
=C2=A0dmesg | grep HPET
[ =C2=A0 =C2=A00.000000] ACPI: HPET 0x00000000BFFE2= 74F 000038 (v01 BOCHS =C2=A0BXPCHPET 00000001 BXPC 00000001)
[ =C2=A0 =C2=A00.000000] ACPI: HPET id: 0x8086a201 base= : 0xfed00000

I seem to indeed have a HPET in my VM= . Does that mean that I should be able to use fq as intended or could the H= PET be some kind of virtualized device?

Regards,
Hans-Kristian=C2=A0
On 25 January 2017 at 22:09, Jonathan Morton <= span dir=3D"ltr"><chromatix99@gmail.com> wrote:

> On 25 Jan, 2017, at 23:05, Hans-Kristian Bakke <hkbakke@gmail.com> wrote:
>
> Do I understand correctly that fq is really just hit and miss within a= VM in general then? Is there no advantage to the fair queing part even wit= h a low-precision clock?

First, check using dmesg or whatever that you do, or do not, have a = working HPET within your VM.

If this is a widespread problem, I could concoct a patch to sch_fq which co= mpensates for it.=C2=A0 I already fixed the same problem when using part of= sch_fq as a basis for part of sch_cake, and demonstrated correct operation= on an old, slow PC without an HPET.

=C2=A0- Jonathan Morton


--94eb2c03c39ab780fb0546f1b5f3--