From: Hans-Kristian Bakke <hkbakke@gmail.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Initial tests with BBR in kernel 4.9
Date: Wed, 25 Jan 2017 22:13:52 +0100 [thread overview]
Message-ID: <CAD_cGvH8DjPvvj8=jKZhMH7AQ91N5Bsi6o9pdUzt6exX3rqN6Q@mail.gmail.com> (raw)
In-Reply-To: <908CA0EF-3D84-4EB4-ABD8-3042668E842E@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1090 bytes --]
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 <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 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
>
>
[-- Attachment #2: Type: text/html, Size: 1778 bytes --]
next prev parent reply other threads:[~2017-01-25 21:13 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 20:54 Hans-Kristian Bakke
2017-01-25 21:00 ` Jonathan Morton
[not found] ` <CAD_cGvHKw6upOCzDbHLZMSYdyuBHGyo4baaPqM7r=VvMzRFVtg@mail.gmail.com>
2017-01-25 21:09 ` [Bloat] Fwd: " Hans-Kristian Bakke
[not found] ` <908CA0EF-3D84-4EB4-ABD8-3042668E842E@gmail.com>
2017-01-25 21:13 ` Hans-Kristian Bakke [this message]
2017-01-25 21:17 ` [Bloat] " Jonathan Morton
2017-01-25 21:20 ` Hans-Kristian Bakke
2017-01-25 21:26 ` Jonathan Morton
2017-01-25 21:29 ` Hans-Kristian Bakke
2017-01-25 21:31 ` Hans-Kristian Bakke
2017-01-25 21:42 ` Jonathan Morton
2017-01-25 21:48 ` Eric Dumazet
2017-01-25 22:03 ` Hans-Kristian Bakke
2017-01-25 21:03 ` Hans-Kristian Bakke
2017-01-25 22:01 ` Neal Cardwell
2017-01-25 22:02 ` Neal Cardwell
2017-01-25 22:12 ` Hans-Kristian Bakke
2017-01-25 22:06 ` Steinar H. Gunderson
2017-01-25 22:12 ` Eric Dumazet
2017-01-25 22:23 ` Steinar H. Gunderson
2017-01-25 22:27 ` Eric Dumazet
2017-01-25 22:38 ` Hans-Kristian Bakke
2017-01-25 22:48 ` Neal Cardwell
2017-01-25 23:04 ` Hans-Kristian Bakke
2017-01-25 23:31 ` Hans-Kristian Bakke
2017-01-25 23:33 ` Eric Dumazet
2017-01-25 23:41 ` Hans-Kristian Bakke
2017-01-25 23:46 ` Eric Dumazet
2017-01-25 23:47 ` Hans-Kristian Bakke
2017-01-25 23:53 ` Eric Dumazet
2017-01-25 23:56 ` Hans-Kristian Bakke
2017-01-26 0:10 ` Eric Dumazet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAD_cGvH8DjPvvj8=jKZhMH7AQ91N5Bsi6o9pdUzt6exX3rqN6Q@mail.gmail.com' \
--to=hkbakke@gmail.com \
--cc=bloat@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox