From: "Joel Wirāmu Pauling" <joel@aenertia.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>,
Cake List <cake@lists.bufferbloat.net>,
make-wifi-fast@lists.bufferbloat.net,
cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Make-wifi-fast] [Cerowrt-devel] meltdown update for bufferbloat.net
Date: Fri, 12 Jan 2018 15:18:30 +1300 [thread overview]
Message-ID: <CAKiAkGSWNP=L-NP=UZfkjTH7_DoqrY-0oq4bcYL6y=yjo=+1hw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw46+syqPQDg33T31qX0rpEGSQ=2Et4_L0-JUyjM9pG_=A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]
I am planing on running thunderbolt3 network flent RRUL test pre and post
KPTI patch set.
On 12 January 2018 at 15:09, Dave Taht <dave.taht@gmail.com> wrote:
> I have rebooted all 7 of the bufferbloat.net servers on linode into
> their post-meltdown-fix 4.14.12 kernel. I am pretty sure the
> underlying substrates are migrated also.
> (https://blog.linode.com/2018/01/03/cpu-vulnerabilities-meltdown-spectre/
> )
>
> I'd be interested in higher speed rrul/etc tests against
> flent-fremont, etc, to see if anything changed. For all i know some
> things changed for the better, there were a few places where linode
> told me had gone from a 250Mbit to 1gbit limit.
>
> No fixes for spectre are available as yet, and of course the meltdown
> fixes being so new will have their own problems.
>
> Please let me know if i broke anything else. I'd never rebooted
> *everything* before.
>
> I still have a ton of other boxes to fix behind the now disabled vpn,
> made more difficult by my habit of hacking on kernels of various
> ages... I only have a couple OOO arms....
>
> I tend to think that rerolling crypto keys (SSL and ssh) would be prudent.
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 2152 bytes --]
prev parent reply other threads:[~2018-01-12 2:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 2:09 [Make-wifi-fast] " Dave Taht
2018-01-12 2:18 ` Joel Wirāmu Pauling [this message]
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/make-wifi-fast.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKiAkGSWNP=L-NP=UZfkjTH7_DoqrY-0oq4bcYL6y=yjo=+1hw@mail.gmail.com' \
--to=joel@aenertia.net \
--cc=bloat@lists.bufferbloat.net \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=make-wifi-fast@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