News for hackers. Stuff that matters.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by vardump on Wednesday January 03, 2018 @10:43AM (#16061878)
> From what I've read, this slowdown only affects syscalls

Incorrect. It also affects interrupts and (page) faults.

Any usermode to kernel and back transition.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by api on Wednesday January 03, 2018 @10:52AM (#16061963)
So this is evil for virtualization hosting, which is the major enterprise application for Intel chips.

Hosting on bare metal will become more attractive. Too bad you can't long OVH and Hetzner.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by chrisper on Wednesday January 03, 2018 @11:31AM (#16062360)
>Too bad you can't long OVH and Hetzner.

What does that even mean?

Also Hetzner just introduced some AMD Epyc server.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by golfer on Wednesday January 03, 2018 @11:37AM (#16062436)
"Long" as a verb means to purchase their stock.

As opposed to "shorting" a stock, which means making a bet that it will go down in value.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by chrisper on Wednesday January 03, 2018 @11:46AM (#16062544)
Ah that makes sense. Thanks!
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by rbjorklin on Wednesday January 03, 2018 @11:40AM (#16062468)
For some reason I can’t reply to ‘chrisper’ but I think ‘api’ is referring to going long in the stock market.

https://www.investopedia.com/terms/l/long.asp

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by Splines on Wednesday January 03, 2018 @12:13PM (#16062780)
> For some reason I can’t reply to ‘chrisper’

HN doesn't let you do this to new comments to avoid back-and-forth commenting that is typical in flamewars.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by sli on Wednesday January 03, 2018 @12:57PM (#16063242)
Coming up on 9 years here and I'm still finding out new things about how this site works. I've been wondering recently why some comments aren't replyable.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by jfoutz on Wednesday January 03, 2018 @01:27PM (#16063564)
I think there is a time delay. Wait a few minutes or hours and you can reply. That cooling off period has helped me really think through my replies.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by AnimalMuppet on Wednesday January 03, 2018 @01:59PM (#16063928)
They become replyable after some amount of time. The amount of time varies based on how active the thread is and/or how deeply nested the comment is.

You can reply anyway, but you have to click on the timestamp ("X minutes ago") to do it.

Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by pbhjpbhj on Wednesday January 03, 2018 @01:20PM (#16063485)
Usually you can click on the <posting time> and go to a page that displays only that comment, which has a reply box even when there's no reply option on the main page.
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by bandrami on Wednesday January 03, 2018 @02:08PM (#16064006)
That 100Hz timer tunable just got a lot more attractive...
Re:Intel Confronts Potential ‘PR Nightmare’ With Reported Ch... by dx034 on Thursday January 04, 2018 @07:17AM (#16069773)
Does that mean that you can get an instance on AWS and slowdown the underlying server for all others by forcing a lot of syscalls? Or how is performance distributed between tenants?