I think if the benchmark is write intensive, this could happen. When DRAM controller process writes, if there are many writes(cache evictions) arrives at a rate faster than the rate at which DRAM controller process writes.
Thanks, Prathap On Tue, Jul 14, 2015 at 11:27 AM, Prathap Kolakkampadath < [email protected]> wrote: > Hello Users, > > I am using classic memory system with following DRAM controller parameters > write_buffer_size = 64 > write_high_thresh_perc = 85 > write_low_thresh_perc = 50 > min_writes_per_switch =18 > > According to write draining algorithm, the bus has to turn around to > writes when the > writeQueue.size() > writeHighThreshold. However when i run some memory > intensive benchmarks, i get a high number of Write retry requests because > the write queue is full, as reported in the gem5 statistics. > # Number of times write queue was full causing retry > system.mem_ctrls.numWrRetry 183731 > > > I am not sure how this could happen, as the DRAM controller drain writes > in a batch whenever the write queue size grows beyond the high threshold, > which is only 85% of Write Buffer Size. Is this expected? > > Thanks, > Prathap >
_______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
