Re: [Gems-users] CONFIG_FETCH_THREADS_PER_CYCLE parameter in GEMS2.1

["Daniel Sánchez Pedreño" <sanatox@xxxxxxxxx>]

I would suggest for the condition:

if(num_fetched[proc] >1 ){

because if the first fetched instruction is a ITLB_MISS num_fetched[proc] would be 1 but no instructions has been really fetched. However, if the ITLB_MISS is in the second or third fetched instruction num_fetched[proc] will be greater than 1 and some instructions have been really fetched.

Regards,

Dani

On Wed, Sep 10, 2008 at 6:28 PM, Daniel Sánchez Pedreño <sanatox@xxxxxxxxx> wrote:

Dear list, as I've seen in config/config.defaults, CONFIG_FETCH_THREADS_PER_CYCLE  "specifies how many threads to fetch from in each cycle". However, I've seen that instructions from different threads can be fetched in the same cycle. This situation happens  when a thread fetches some instructions normally but the final one is not because of a cache or itlb miss. The problem is that altough this thread has fetched normally several instructions num_thread_fetched is not incremented so another thread is able to fetch.

I think this behaviour is not correct if we have set CONFIG_FETCH_THREADS_PER_CYCLE to 1, but I would like a confirmation.

--
http://sanatox.es