From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-x243.google.com (mail-oi0-x243.google.com [IPv6:2607:f8b0:4003:c06::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 E21143B29E for ; Wed, 25 Jan 2017 16:20:01 -0500 (EST) Received: by mail-oi0-x243.google.com with SMTP id w144so16653133oiw.1 for ; Wed, 25 Jan 2017 13:20:01 -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 :cc; bh=3plRFsq2Ma7T+r1TgrIXbXiEsQXqMxuugotgWAaXra0=; b=LkGJD6b/u6sB5N46ggxcVETfJsAqNqEGtRNDUebM8SFqCQCarkgeea/gDNI2q4gggl UBuyYwHKBZ6PReWBIDWBuKtOnPP35bMJo3yp6GHItU8LXY3aeUjlzUo+CMyKsoIVinwg 5BGPGnSgY1JidDNVIwcGS1OAkiFUfb8UslIeAggWdj1YB4ebNqdHvekcvMmMYJKNdLzr 1M0ToP08XyNHpr+5Sqx4ymEYmsUKG9Ftad1L+GS9inDuluPaxI/FwfosATjt3jV6Fl+j WJ80nIB0a+T+2Po3CgghVqTg6EVSCDimcQVxswZp01WMd3VYrBTxt5f/cKCdUefzHEBH A5Yg== 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:cc; bh=3plRFsq2Ma7T+r1TgrIXbXiEsQXqMxuugotgWAaXra0=; b=q4O7FqXLQ9Mn8Vvp7lK+Fc3vLqVsbvRCBND+iSObz8u3LBe+hU2Yzom0FUaAwuc0c4 6k3gLwlruPG7ckMGsd7+tBON4294fgg54njZvFaylmFupUUTiMWjhA0DPnOgewgBL3AS Ef2sp8BHHoo0oxwAqM/wnHljH7VbN2kDq+VE9DqlS58LyJC150zya6JXXzWlz3svtUwN VWTdHjNL+ehXqaHCfQ7rsf6XJz1isdLELZ8lvk+hmhzKnp14SXbIsUbJ+vylnjKoreMn /xFZzAMiGuAnuQxANZiRHePiXAnccKNwZJPyISJ/ltCw9wf1kAo2Xqu+K6zAAh7gqYTm 7pVg== X-Gm-Message-State: AIkVDXIPIu+XTTt7hzbcK/PdpnkJHeVULLfsmNpzRf0HknW9uEUsPkWGWoI0RkohVCUlk8bXhjyDMFB8BiG28Q== X-Received: by 10.202.253.206 with SMTP id b197mr21679554oii.160.1485379201257; Wed, 25 Jan 2017 13:20:01 -0800 (PST) MIME-Version: 1.0 Received: by 10.157.1.21 with HTTP; Wed, 25 Jan 2017 13:20:00 -0800 (PST) In-Reply-To: <8B89C257-99D4-4A9A-96ED-A103A2089A46@gmail.com> References: <58D7E8D3-5661-4126-80D9-2F2D4E478B10@gmail.com> <908CA0EF-3D84-4EB4-ABD8-3042668E842E@gmail.com> <8B89C257-99D4-4A9A-96ED-A103A2089A46@gmail.com> From: Hans-Kristian Bakke Date: Wed, 25 Jan 2017 22:20:00 +0100 Message-ID: To: Jonathan Morton Cc: bloat@lists.bufferbloat.net Content-Type: multipart/alternative; boundary=001a113de104a5d8300546f1cb65 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:20:02 -0000 --001a113de104a5d8300546f1cb65 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable This is the output from =E2=80=8B"dmesg | fgrep -i hpet": =E2=80=8B[ 0.000000] ACPI: HPET 0x00000000BFFE274F 000038 (v01 BOCHS BX= PCHPET 00000001 BXPC 00000001) [ 0.000000] ACPI: HPET id: 0x8086a201 base: 0xfed00000 [ 0.000000] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604467 ns [ 0.000000] hpet clockevent registered [ 0.362335] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0 [ 0.362339] hpet0: 3 comparators, 64-bit 100.000000 MHz counter [ 0.661731] rtc_cmos 00:00: alarms up to one day, y3k, 114 bytes nvram, hpet irqs On 25 January 2017 at 22:17, Jonathan Morton wrote: > > > On 25 Jan, 2017, at 23:13, Hans-Kristian Bakke > wrote: > > > > dmesg | grep HPET > > [ 0.000000] ACPI: HPET 0x00000000BFFE274F 000038 (v01 BOCHS BXPCHPE= T > 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? > > Try =E2=80=9Cdmesg | fgrep -i hpet=E2=80=9D - that=E2=80=99ll also tell y= ou whether you have > drivers for your HPET device, and whether it is being used. > > - Jonathan Morton > > --001a113de104a5d8300546f1cb65 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
This is the output from =E2=80=8B&= quot;dmesg | = fgrep -i hpet":

=E2=80=8B[ =C2=A0 =C2=A00.000000] = ACPI: HPET 0x00000000BFFE274F 000038 (v01 BOCHS =C2=A0BXPCHPET 00000001 BXP= C 00000001)
[ =C2=A0 =C2=A00.000000] ACPI: HPET id: 0x8086a201 base: 0xfed0= 0000
[ =C2=A0 =C2=A00.000000] clocksource: hpet: mask: 0xffffffff max_cycle= s: 0xffffffff, max_idle_ns: 19112604467 ns
[ =C2=A0 =C2=A00.000000] hpet cl= ockevent registered
[ =C2=A0 =C2=A00.362335] hpet0: at MMIO 0xfed00000, IRQ= s 2, 8, 0
[ =C2=A0 =C2=A00.362339] hpet0: 3 comparators, 64-bit 100.000000 = MHz counter
[ =C2=A0 =C2=A00.661731] rtc_cmos 00:00: alarms up to one day, = y3k, 114 bytes nvram, hpet irqs


<= br>
On 25 January 2017 at 22:17, Jonathan Morton = <chromatix99@gmail.com> wrote:

> On 25 Jan, 2017, at 23:13, Hans-Kristian Bakke <hkbakke@gmail.com> wrote:
>
> dmesg | grep HPET
> [=C2=A0 =C2=A0 0.000000] ACPI: HPET 0x00000000BFFE274F 000038 (v01 BOC= HS=C2=A0 BXPCHPET 00000001 BXPC 00000001)
> [=C2=A0 =C2=A0 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 d= evice?

Try =E2=80=9Cdmesg | fgrep -i hpet=E2=80=9D - that=E2=80=99ll also t= ell you whether you have drivers for your HPET device, and whether it is be= ing used.

=C2=A0- Jonathan Morton


--001a113de104a5d8300546f1cb65--