~ 37 GFLOPS/W is probably a better projection if we assume (out of nowhere) that the theoretical/achieved ratio of Frontier is comparable to Summit (75%). Still very impressive.
1,101 karma · joined January 24, 2018
~ 37 GFLOPS/W is probably a better projection if we assume (out of nowhere) that the theoretical/achieved ratio of Frontier is comparable to Summit (75%). Still very impressive.
i9-7960X: 1024 KiB L2/core, 1.375 MiB L3/core
Seems to be exactly what I described? L2/core went up by 768 KiB, L3/core went down by 1.125 MiB.
I wonder if that will be the case on Frontier.
The change to a non-inclusive L3 is more likely to contribute to greater capacity.
> but the mechanism behind this is entirely hand-waving.
The objective of this paper was not to specify, or even attempt to specify, the mechanism.
> The paper's use of machine learning seems entirely pointless, basically drawing the obvious line between the two sets of points.
Yeah, that is pretty much the entire objective of SVMs.
Please clarify how you think that statement is incorrect. As far as I'm concerned, it won't die because that's how virtual memory works, and you have something going on in your head that is either wrong or massive hairsplitting.
I would have expected a better understanding from someone bloviating about how the try of the commenters are too thick to understand mmap and virtual memory.
> nobody has ever suggested avoiding virtual memory except you
Do you know what the "anonymous" in "anonymous mapping" means? You are the one that started asserting that anonymous mapping from mmap have the same difficulties as mapping of normal files and therefore too dangerous to use.
If you apply the same reasoning that you've used to conclude that everyone should avoid mmap, than you are led directly to the conclusion that everyone should avoid virtual memory.
The "same problems" that you are pointing out are possible with anonymous memory aren't unique to memory you get directly from mmap, they also apply to all memory, period. mmap'ed anonymous memory might have th same problems as file-backed memory, but those are the same problems that .text and .bss have.
The "powerful (and consequently hazardous) OS feature" here isn't mmap, it's literally virtual memory. At the moment you concede that memory may be backed by something besides physical memory at any point in time, you get the possibility of all those "exotic error paths."
"There is probably enough evidence in this thread to use it as a reference for why typical apps should avoid virtual memory whenever possible -- it's clear almost nobody fully understands it"
I'd suggest that is ludicrous, and for the same reason your original conclusion is also excessive.
It seems clear that you aren't actually interested primarily in sound the cool things, but doing more cool things earlier than peers.
A few percent better than "humans" is quite bad relative to a semi-responsible human driver.
Erm, what?
> what about Socrates?
Erm, what?
And that is a different discussion. The article, and the discussion here, is regarding side channels attacks within a single process. I'm pretty sure everyone agrees that the hardware (or some conspiracy of the hardware and kernel) must provide process isolation.
Keep in mind you've cited probably the first or second most expensive mile of any subway ever built, and subways usually cost much more than other trains.
China regularly builds high speed rail for $30M per mile. Europe is usually closer to $50-60M. Tokyo has built subways for $400M per mile.
https://www.nytimes.com/2017/12/28/nyregion/new-york-subway-...
I find it interesting that the apparent objective is to make driving safer, but apparently the powers that be have decided that it is easier to make cars that drive themselves than to convince people not to drive while drunk.
And self-driving cars don't? How many trains could be built with the billions invested so far in self-driving cars?
What do you have in mind? The stanford elites get to live in san francisco, and the less-elite get shipped elsewhere?
> ur died, Babylon died.
Your two examples are from 2-3 millennia ago. I would think if cities "die all the time," you would have more recent examples.
Maybe it proves the author correct that the first cities that came to mind are from 2500 years ago?
I don't think there are other major cities where the population is < 14% children. NYC is around 24%.
Your view of the "pretty good community" is irrelevant. Compared to other cities, San Francisco has "very few kids/families."