Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
dfrage
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
11 ms
·
61.
▲
by
dfrage
7y ago
> This is clearly what Intel did. And ARM, and IBM, both the POWER and mainframe/Z teams. Although this design decision of Intel's was in the early 1990s, shipping in their first Pentium Pro in 1995. When AMD's competitio
62.
▲
by
dfrage
7y ago
> Because implementing it increased performance which made the numbers which captured market share. More than the following big things, in both directions? - A consistent fabrication advantage until very recently? That's said to ha
63.
▲
by
dfrage
7y ago
And for Intel these bugs go back to the first Pentium Pro in 1995, their first out-of-order speculative execution design. Very cunning of them, along with IBM two years earlier, the SPARC bunch starting that year, MIPS and AMD a year later
64.
▲
by
dfrage
7y ago
Expanding on your points, only AMD, SPARC and MIPS avoided Meltdown bugs, they were also found in ARM, and IBM POWER and mainframe/Z designs. All of these vendors have out-of-order speculative execution designs that are vulnerable t
65.
▲
by
dfrage
7y ago
I remember reading that Intel was having TSMC run off the lowest end Altera FPGAs because Intel's fabs were just too expensive. Other possibilities off the top of my head might be Cadence being able to do stuff that's now required
66.
▲
by
dfrage
7y ago
They used to charge serious money for it, that would have allowed them the budget to fix enough of the bugs that SMS is now pretty damned good. Culture is also a large part of it, it's embedded in telcos to such a degree that I and my
67.
▲
by
dfrage
7y ago
The OP is an Android developer, eating the $70 dollars was part of the cost of continuing to do that business. But it's not going to help their brand or encourage others who are too tied to Google to sign on to services like Fi, and if
68.
▲
by
dfrage
7y ago
Too many people have too much of Google as part of their lives to do more than the OP did and eat the $70 instead of dropping out of Android development. And that's got to be how Google can, intentionally or not, get away with such bla
69.
▲
by
dfrage
7y ago
Even in Texas you aren't going to get away with "defending" yourself in this situation without a real physical threat. And gun owners know that, there are very few unjustified shootings of bill collectors or the like, and th
70.
▲
by
dfrage
7y ago
For lots of people, because that would cost them all their other Google accounts and services. The OP would have to give up on Android development. I am former Fi user, started back when it was a "Project". My Nexus 5X's ba
71.
▲
by
dfrage
7y ago
Note on the engine math: this is a fully reusable rocket, both stages, so on a Mars missions the 31 in the booster would in theory be recovered for future launches from the Earth. Getting the seven back from the 2nd stage, well, maybe soon
72.
▲
by
dfrage
7y ago
It's pretty clear it wasn't pervasive for ARM because they're climbing to ever higher performance, while Intel reached a conceptual peak in 1995 with the Pentium Pro, and in turn has used mostly Pentium superscalar based core
73.
▲
by
dfrage
7y ago
> Other companies didn’t do this. ARM, and IBM POWER and mainframe/Z also did that (Meltdown): https://en.wikipedia.org/wiki/Meltdown_(security_vulnerabili... ARM also has a Rogue System Register Read vulnerab
74.
▲
by
dfrage
7y ago
As a friend and coworker liked to say, "speed kills", and Google is right that it's a risk, just one a lot of people are willing to take. Every company with high performance single thread designs has out-of-order with specula
75.
▲
by
dfrage
7y ago
When the penalty for revealing it would likely be execution for high treason?
76.
▲
by
dfrage
7y ago
While I'm entirely satisfied with the simple Oswald explanation, you are correct to emphasis how utterly terrible JFK's defense and foreign policy was. The severe weakness shown in the Bay of Pigs debacle, an Eisenhower scheme he
77.
▲
by
dfrage
7y ago
Isn't one of the "secrets" to AMD's post-486 success adopting the general approach the Pentium Pro took along with others in the 1990s, which in turn are based on IBM's 1960s Tomasulo out-of-order algorithm adding s
78.
▲
by
dfrage
7y ago
Because that logic is the same of the drunk looking for his car keys under the street light, rather than the dark area were he lost them. AMD's server market share is minuscule and dropped as of 19Q1, 3.2% to 2.9%, although healthier a
79.
▲
by
dfrage
7y ago
Which didn't save AMD from Spectre bugs. And everyone else with high performance speculative execution out-of-order designs also had Meltdown bugs, ARM and IBM, both POWER and mainframe/Z: https://en.wikipedia.org/
80.
▲
by
dfrage
7y ago
ARM is more less examined than less vulnerable. Most of their cores aren't speculative execution out-of-order, that's expensive in power and silicon real estate/cost, but they have 13 vulnerable to Spectre, including 1 known
81.
▲
by
dfrage
7y ago
That any discussion of your potential customers "inside" the office, purely between people in your company, is highly to entirely speculative. You've got to get "out" of the office and sell your product, or not, to
82.
▲
by
dfrage
7y ago
> All the standard business knowledge and tech knowledge that is common knowledge today had not yet been figured out. You're right about that. The lean startup, "there's no truth in the office", Minimum Viable Produc
83.
▲
by
dfrage
7y ago
One thing to focus on is how much of the crash was telecom vs. dot.com companies. An excess of fiber was laid, which was a boon to later companies like Google which bought dark fiber at low prices, competitive local exchange carriers (CLEC
84.
▲
by
dfrage
7y ago
> #2 aggregated the bugs rolling in for more than a year to minimize impact. When the impact is new microcode for every out-of-order CPU going back to Sandy Bridge that's not on its face entirely unreasonable. The date for the new
85.
▲
by
dfrage
7y ago
There's also Same OS, operating system level virtualization, like Docker, it's the less expensive default for https://www.ramnode.com/vps.php for example. Not at all familiar with this technology, but scanning Wi
86.
▲
by
dfrage
7y ago
> different trust domain cannot seriously benefit from a common cache: their datasets are by definition disjoint. Datasets, yes, but what about instructions from shared libraries? I'll make a wild guess this being seriously benefici
87.
▲
by
dfrage
7y ago
> It's interesting though why cross-process data exfiltration based on speculative execution was not tried with any success in the shared hosting environment of 1990s and early 2000s. According to several of the researchers who foun
88.
▲
by
dfrage
7y ago
I touch on it here: https://news.ycombinator.com/item?id=19650813 which includes a link to their paper on it.
89.
▲
by
dfrage
7y ago
Good point, I was thinking in the context of owning your own (super)computer or mainframe and having control over what ran on it. In the cloud, which to us implies running in a VM with other tenants vs. for example dedicated machine(s) wit
90.
▲
by
dfrage
7y ago
In theory is was going to be a bit better than TSMC 7mm, with only 7+nm equaling or exceeding it. In practice, it's slower than Intel 14nm, denser (better be!!), and consumes less power. And has pesky yield issues, Semiaccurate is
More ›