I don't think he does. What he describes is part of what myself and my colleagues consider "computer science." We typically consider "computer engineering" the design and making of hardware. But to be a systems researcher in computer science, you must know how these things work, and be able to reason about how they affect the software systems you care about.