News for hackers. Stuff that matters.
Re:How to Interview Engineers by pogaxvr on Tuesday June 27, 2017 @10:30AM (#14645690)
Clock rate != operations. It's like you didn't bother to read what I wrote.
Re:How to Interview Engineers by detaro on Tuesday June 27, 2017 @10:44AM (#14645822)
Closely enough related to number of basic operations though I'd say. I'll agree with you if it really just is a multiple choice question without context, but the initial poster did not present it that way, but said that explanation/discussion matters. And then your objections are a good starting point for that.
Re:How to Interview Engineers by 0xbear on Tuesday June 27, 2017 @01:41PM (#14647493)
The worst thing you realistically can do to stall your CPU is miss cache every time you read data from RAM. If you do this for every instruction (which would be quite a feat in itself), you divide your instruction throughput by about 200. But even then, and even on the shittiest modern CPU you'll be retiring millions of instructions per second.
Re:How to Interview Engineers by pogaxvr on Wednesday June 28, 2017 @05:40PM (#14658738)
The MSP430, released in 2010, can be clocked down to 32kHz. That's pretty much the state of the art in modern, low-power devices.
Re:How to Interview Engineers by 0xbear on Wednesday June 28, 2017 @09:52PM (#14660170)
And if you know that, I'm pretty sure you'd pass that interview.