From: Michael Richardson <mcr@sandelman.ca>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] bufferbloat vs NetSpectre
Date: Mon, 30 Jul 2018 22:59:06 -0400 [thread overview]
Message-ID: <22964.1533005946@localhost> (raw)
In-Reply-To: <CAA93jw6xj_-qUaeHBn-aoCKGAzG+KF0f3dCqcatYSAshUU6Mng@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]
I was reading through the NetSpectre paper at:
http://misc0110.net/web/files/netspectre.pdf
I haven't finished it all yet... key thing was on page 5, which starts with:
if (x < bitstream_length)
if(bitstream[x])
flag = true
As I understand it, they are depending error packets that come back to
measure cache fills from a background of packets that fail tests such as
above.
Two things occur to me:
1) in a really badly bufferbloated network, the
super-long queues ought to completely screw things up for them.
2) fq_codel ought to something significant to the measurements.
I don't know yet if it might them better or worse. But,
it ought to do something.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 464 bytes --]
parent reply other threads:[~2018-07-31 2:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAA93jw6xj_-qUaeHBn-aoCKGAzG+KF0f3dCqcatYSAshUU6Mng@mail.gmail.com>]
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=22964.1533005946@localhost \
--to=mcr@sandelman.ca \
--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