News for hackers. Stuff that matters.
Re:In mobile, 62.7% of computation energy cost is spent on d... by pjc50 on Wednesday November 27, 2019 @06:05AM (#21646926)
Including a copy of Maslow's hierarchy of needs and some green field vs factory slides seems to be .. overselling it a bit?

Fortunately it pulls back towards a "what are the easy wins" approach: in-memory initialising (rather than stream zeroes over the bus, ask the memory to zero itself) and in-memory copy.

The three real problems are:

- this is only useful if the whole stack "knows" about it, or can be transparently optimised to use it. Otherwise the person running a Javascript for loop to set values to zero will ruin it.

- this relies on the data being in DRAM-row-size chunks, and moving it around within the same physical chip. That may also require re-architecting to make that common enough to be useful. Locality issues are the downside to distributed systems; the whole CPU architecture is oriented towards continuing to pretend that everything happens in a defined order in a single place.

- possible security issues (rowhammer?): may seem far off, but if you don't think about it upfront it gets very expensive later.

(Worth recapping: the silicon is fundamentally differently-processed for DRAM, such that implementing complex logic is slow and expensive.)

There are no comments on this comment yet.