3 ms·
As you say, the L1 cache is small. That means you only have to be concerned about it in small time frames (the register set is even smaller, and you don't try t
by Someone 13y ago
As you say, the L1 cache is small. That means you only have to be concerned about it in small time frames (the register set is even smaller, and you don't try to keep stuff in registers across read() calls, either) That read() will block. In the typical HTTP server, that means other code will run and fill the L1 cache with its data. There's nothing you can do about it in a HTTP server.
And, pedantic: thatread() should use DMA to move in the data, in which case it needn't hit the L1 cache.