t 20:36
To: gpfsug main discussion list
<gpfsug-discuss@spectrumscale.org<mailto:gpfsug-discuss@spectrumscale.org>>
Subject: Re: [gpfsug-discuss] Meltdown, Spectre, and impacts on GPFS
Kevin,
The team is aware of Meltdown and Spectre. Due to the late availability of
production-ready
to the Spectrum Scale (GPFS) team.
From: "Avila-Diaz, Leandro" <lav...@illinois.edu>
To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org>
Date: 03/01/2018 11:17 PM
Subject: Re: [gpfsug-discuss] Meltdown, Spectre, and impacts on GPFS
Sent by:
list <gpfsug-discuss@spectrumscale.org>
Date: Thursday, January 4, 2018 at 20:36
To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org>
Subject: Re: [gpfsug-discuss] Meltdown, Spectre, and impacts on GPFS
Kevin,
The team is aware of Meltdown and Spectre. Due to the late ava
...@spectrumscale.org
<gpfsug-discuss-boun...@spectrumscale.org> on behalf of Buterbaugh, Kevin L
<kevin.buterba...@vanderbilt.edu>
Sent: Monday, January 8, 2018 5:52 PM
To: gpfsug main discussion list
Subject: Re: [gpfsug-discuss] Meltdown, Spectre, and impacts on GPFS
Hi GPFS Team,
Thanks for t
u>>
To: gpfsug main discussion list
<gpfsug-discuss@spectrumscale.org<mailto:gpfsug-discuss@spectrumscale.org>>
Date: 01/04/2018 01:11 PM
Subject: [gpfsug-discuss] Meltdown, Spectre, and impacts on GPFS
Sent by:
gpfsug-discuss-boun...@spe
mscale.org>
Subject: [gpfsug-discuss] Meltdown, Spectre, and impacts on GPFS
Message-ID: <5d655862-7f60-47f6-8bd2-a5298f73f...@vanderbilt.edu>
Content-Type: text/plain; charset="utf-8"
Happy New Year everyone,
I?m sure that everyone is aware of Meltdown and Spectre by
Kevin L" <kevin.buterba...@vanderbilt.edu>
To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org>
Date: 01/04/2018 01:11 PM
Subject: [gpfsug-discuss] Meltdown, Spectre, and impacts on GPFS
Sent by:gpfsug-discuss-boun...@spectrumscale.org
Happy N
While I'm not fully versed on the vulnerability or the proposed fixes,
my understanding is that most of the performance impact from the fix is
around having kernel memory completely separately from a process's
user-space, which means every system call will have cache/TLB misses.
This might mean
