Hi Travix, I believe Garnet (and/or Ruby) can only support 64 cores. They use a 64 bit number as a mask for the cores. To fix this, we'll need to dig in and replace all of those explicitly sized variables with vector<bool>. I don't think it's actually that many plance that need to change, but it's been a while since I've looked into it.
The _intlv_match (interleaving bits match) may be a different problem. This could be caused by trying to use the wrong bits to interleave the directory addresses. I would carefully check the config file you're using to dig into how the addresses are being interleaved at either the L2 and/or directory levels. Generally, gem5 hasn't been used much with core counts above 64, so, there may be a number of bugs that are exposed. We would appreciate contributions to help us improve things! Cheers, Jason On Thu, May 27, 2021 at 5:31 PM Travis Dai via gem5-users < gem5-users@gem5.org> wrote: > Hi all users, > > > > I have implemented a ring topology in gem5, it works well when set up > nodes number = 64. > > > > When I set cpu =60, I met the following error: “fatal: fatal condition > !masks.empty() && _intlv_match >= ULL(1) << masks.size() occurred: Match > value 32 does not fit in 5 interleaving bits. Memory Usage: 149132 KBytes” > > > > When I set cpu =128/256, I met the following error: “fatal: Number of > bits(64) < size specified(65). Increase the number of bits and recompile. > Memory Usage: 856144 KBytes” > > > > Does anyone know the reason? > > > > Best, > > Travis > > > _______________________________________________ > gem5-users mailing list -- gem5-users@gem5.org > To unsubscribe send an email to gem5-users-le...@gem5.org > %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
