Re: [OMPI users] latest Intel CPU bug

2018-01-05 Thread Jeff Hammond
An article with "market share" in the title is not a technical assessment, but in any case, you aren't willing to respect the request to focus on Open-MPI on the Open-MPI list, so I'll be piping mail from your address to trash from now on. Jeff On Thu, Jan 4, 2018 at 10:54 PM, John Chludzinski <

Re: [OMPI users] latest Intel CPU bug

2018-01-05 Thread r...@open-mpi.org
That is enough, folks. This is an email forum for users to get help regarding Open MPI, not a place to vent your feelings about specific vendors. We ask that you respect that policy and refrain from engaging in such behavior. We don’t care if you are quoting someone else - the fact that “Mikey

Re: [OMPI users] latest Intel CPU bug

2018-01-05 Thread Ray Sheppard
Hello All,   Please people, just drop it.  I appreciated the initial post in response to to the valid question of how these bugs might impact OMPI and message passing in general.  At this point, y'all are beating the proverbial dead horse.  If you wish to debate, please mail each other

Re: [OMPI users] latest Intel CPU bug

2018-01-05 Thread John Chludzinski
I believe this snippet sums it up pretty well: "Now you have a bit more context about why Intel’s response was, well, a non-response. They blamed others, correctly, for having the same problem but their blanket statement avoided the obvious issue of the others aren’t crippled by the effects of

Re: [OMPI users] latest Intel CPU bug

2018-01-05 Thread Matthieu Brucher
Hi, I think, on the contrary, that he did notice the AMD/ARM issue. I suppose you haven't read the text (and I like the fact that there are different opinions on this issue). Matthieu 2018-01-05 8:23 GMT+01:00 Gilles Gouaillardet : > John, > > > The technical assessment so

Re: [OMPI users] latest Intel CPU bug

2018-01-04 Thread Gilles Gouaillardet
John, The technical assessment so to speak is linked in the article and is available at https://googleprojectzero.blogspot.jp/2018/01/reading-privileged-memory-with-side.html. The long rant against Intel PR blinded you and you did not notice AMD and ARM (and though not mentionned here,

Re: [OMPI users] latest Intel CPU bug

2018-01-04 Thread John Chludzinski
That article gives the best technical assessment I've seen of Intel's architecture bug. I noted the discussion's subject and thought I'd add some clarity. Nothing more. For the TL;DR crowd: get an AMD chip in your computer. On Thursday, January 4, 2018, r...@open-mpi.org

Re: [OMPI users] latest Intel CPU bug

2018-01-04 Thread r...@open-mpi.org
Yes, please - that was totally inappropriate for this mailing list. Ralph > On Jan 4, 2018, at 4:33 PM, Jeff Hammond wrote: > > Can we restrain ourselves to talk about Open-MPI or at least technical > aspects of HPC communication on this list and leave the stock market

Re: [OMPI users] latest Intel CPU bug

2018-01-04 Thread Jeff Hammond
Can we restrain ourselves to talk about Open-MPI or at least technical aspects of HPC communication on this list and leave the stock market tips for Hacker News and Twitter? Thanks, Jeff On Thu, Jan 4, 2018 at 3:53 PM, John Chludzinski wrote: > From

Re: [OMPI users] latest Intel CPU bug

2018-01-04 Thread John Chludzinski
From https://semiaccurate.com/2018/01/04/kaiser-security-holes-will-devastate-intels-marketshare/ Kaiser security holes will devastate Intel’s marketshareAnalysis: This one tips the balance toward AMD in a big wayJan 4, 2018 by Charlie Demerjian This

Re: [OMPI users] latest Intel CPU bug

2018-01-04 Thread Reuti
Am 04.01.2018 um 23:45 schrieb r...@open-mpi.org: > As more information continues to surface, it is clear that this original > article that spurred this thread was somewhat incomplete - probably released > a little too quickly, before full information was available. There is still > some

Re: [OMPI users] latest Intel CPU bug

2018-01-04 Thread r...@open-mpi.org
As more information continues to surface, it is clear that this original article that spurred this thread was somewhat incomplete - probably released a little too quickly, before full information was available. There is still some confusion out there, but the gist from surfing the various

Re: [OMPI users] latest Intel CPU bug

2018-01-03 Thread r...@open-mpi.org
Well, it appears from that article that the primary impact comes from accessing kernel services. With an OS-bypass network, that shouldn’t happen all that frequently, and so I would naively expect the impact to be at the lower end of the reported scale for those environments. TCP-based systems,

[OMPI users] latest Intel CPU bug

2018-01-03 Thread Noam Bernstein
Out of curiosity, have any of the OpenMPI developers tested (or care to speculate) how strongly affected OpenMPI based codes (just the MPI part, obviously) will be by the proposed Intel CPU memory-mapping-related kernel patches that are all the rage?