01.12.2012 Views

Architecture of Computing Systems (Lecture Notes in Computer ...

Architecture of Computing Systems (Lecture Notes in Computer ...

Architecture of Computing Systems (Lecture Notes in Computer ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

134 M. Kayaalp et al.<br />

Fig. 3. Number <strong>of</strong> concurrently renamed <strong>in</strong>structions<br />

different <strong>in</strong>struction set. These results show that the pipel<strong>in</strong>e stages are full most <strong>of</strong><br />

the cycles as opposed to our previous f<strong>in</strong>d<strong>in</strong>gs obta<strong>in</strong>ed by us<strong>in</strong>g M-Sim [16] for<br />

Alpha 21264 <strong>in</strong>struction set [3].<br />

Fig. 4 shows how much the rename stage is employed <strong>in</strong> two consecutive cycles.<br />

Each horizontal set <strong>of</strong> bars represents a different benchmark and for each benchmark<br />

the statistics show the frequency <strong>of</strong> consecutive employment situation for the rename<br />

stage. For example, the value 44 on the x axis shows how frequent 4 <strong>in</strong>structions are<br />

renamed for two consecutive cycles. The results show that the processor usually<br />

switches between empty stage and full stage but does not usually switch from half-full<br />

to half-full. The frequency <strong>of</strong> 12 and 23 situations show this behavior. Also as it can<br />

be seen from the figure, 40, 30, 20 and 10 situations are quite common (more than<br />

10% on average). Therefore it makes sense to copy a s<strong>in</strong>gle tag to a follow<strong>in</strong>g bubble<br />

slots at a full pipel<strong>in</strong>e stage for s<strong>of</strong>t error detection coverage.<br />

Fig. 4. Frequency <strong>of</strong> employment at the rename stage for two consecutive cycles

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!