I see. It seems like it would be more appropriate to have tester test larger requests because we are getting a false sense of correctness by running the test. It tests the protocol logic well but not the data correctness.
Also, is there a maximum on the size of the m5 request? I would like to test DMA with more realistic requests sizes, like 2048 bytes and larger. Thanks, Polina On Mon, Aug 31, 2009 at 6:16 PM, Steve Reinhardt <[email protected]> wrote: > Good question. Looks like historical cruft to me. I think there used > to be a mode that tested variable-size accesses but that mode got > ripped out. Note that access_size is log2 of the access size, so > setting it to 0 means byte accesses. > > Steve > > On Mon, Aug 31, 2009 at 3:30 PM, Polina Dudnik<[email protected]> wrote: > > Hi, > > > > I have a question: why is it that the access_size is first calculated as > > random() % 4 and then reset to zero before issuing the request in > > MemTest::tick? > > > > Thank you. > > > > Polina > > > > _______________________________________________ > > m5-dev mailing list > > [email protected] > > http://m5sim.org/mailman/listinfo/m5-dev > > > > > _______________________________________________ > m5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/m5-dev >
_______________________________________________ m5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/m5-dev
