News for hackers. Stuff that matters.
Re:Memory FAQ by kensai on Monday October 10, 2016 @02:40PM (#12678988)
Interesting information. But this FAQ collection should have a date. Is it always relevant?
Re:Memory FAQ by schmichael on Monday October 10, 2016 @04:48PM (#12679684)

  ~$ curl -v http://nommu.org/memory-faq.txt > /dev/null
  > GET /memory-faq.txt HTTP/1.1
  > Host: nommu.org
  >
  < HTTP/1.1 200 OK
  < Server: GitHub.com
  < Last-Modified: Thu, 05 May 2016 01:37:27 GMT
Hm, github you say?

https://github.com/nommu/nommu.org

Jun 8, 2015 is the last commit to this particular file.

Re:Memory FAQ by thomaslee on Monday October 10, 2016 @04:43PM (#12679665)
+1 on the date, but generally relevant to most modern x86/x86-64 hardware IMO.

(The rest of this comment is largely my own inflated opinion.)

From a developer's perspective, whether it's _useful_ when operating at a certain level of abstraction is another question. Really do think it's good to know this stuff, but if you're writing, say, Ruby or Python web apps you probably don't _need_ to know it.

Low latency/high throughput/systems-level stuff it starts to become more relevant. That said, there's certainly been operational scenarios where knowing some of this stuff can help narrow down misconfigured systems and/or squeeze more life out of existing hardware (e.g. configuring a JVM to use huge pages).