Hi Korey, I don't seem to have encountered that deadlock threshold when booting the old changeset. I tried both 16 + 20 core configurations just now and they seem to work. Although, they do take a really really long time compared to ~1-4 cores.
I have also tried previously booting 64 cores, some time ago, and that also worked, but that took several hours. In general though, that threshold is just a fixed number, and as the CMP machine gets bigger, the 50000 seems to be way too low, and would have to be multiplied by a factor of 2 -3? I tried using the default crossbar topology, maybe you encounter the deadlock threshold using Mesh? Malek On Fri, Mar 18, 2011 at 12:12 PM, Korey Sewell <ksew...@umich.edu> wrote: > <message below> > > Why did it work before the block size patch? >> - When the ChuckGenerator sees the block size is 0, it doesn't split up the >> request into multiple patches and sends the whole dma request at once. That >> is fine because the DMASequencer splits the request into multiple requests >> and only responds to the dma port when the entire request is complete. >> > With regards to the old changeset that boots with the block size = 0, I was > not able to boot a large scale CMP system (more than 16 cores) due to the > "deadlock threshold" being triggered. > > I'm assuming that Brad has a read on how to fix that problem so I'll > probably start working on what is causing that deadlock so hopefully we can > kind of pipeline the bug fixes. > > -- > - Korey > _______________________________________________ > m5-dev mailing list > m5-dev@m5sim.org > http://m5sim.org/mailman/listinfo/m5-dev > _______________________________________________ m5-dev mailing list m5-dev@m5sim.org http://m5sim.org/mailman/listinfo/m5-dev
