On the face of it, it doesn't sound that bad, but how often does this really occur? If you have a SimObject that regularly has multiple events scheduled at the same tick & priority, and is smart enough to keep track of when that happens, why not have that SimObject chain its own events itself (i.e., it just schedules one event on the event queue but that event has the capability of having additional events tacked on to it).
Steve On Wed, Nov 11, 2009 at 7:29 PM, nathan binkert <[email protected]> wrote: > My simulator basically constantly bangs on the eventq and I had a > revelation. Why not add a version of schedule that can take a hint. > That hint would be another event. If that other event is scheduled > and has the same time and priority, I can insert the new event in the > queue in constant time. I think this sort of thing would come up all > the time. > > The one change that this would have is that currently, the eventq > maintains LIFO order of events with the same time/priority. (It was > at some point fifo actually, but I changed it because I didn't want > people to depend on that.) With this change, the order of events with > the same time/priority would be somewhat chaotic. I think we've > agreed that we make no guarantees on this anyway (and we really > shouldn't if we want to parallelize this thing ever. > > Any reason for me not to add this interface? > > Nate > _______________________________________________ > 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
