Hi Andreas, You've certainly done a lot of work on the code, so I'm interested in hearing more about your rationale for the name change. However, to me, it looks like a set of parallel independent buses... unless things have changed more than I realize. For each bus (layer), you only have one sender at a given point in time, and---at least for snoop requests---that sender's data is broadcast to all the receivers, right?
I see that there's an isomorphism to a crossbar there, but to me it's still logically operating as a set of busses, since (for example) you can't have independent responses (from different sources to different destinations) transmitted at the same time---which is what a crossbar would imply to me. Or is that possible now? I checked the code, and since each layer has a single IDLE/BUSY/RETRY state, I'm guessing not, but I only glanced at the code, so I may have missed something. Thanks, Steve On Sun, Mar 23, 2014 at 9:37 AM, Andreas Hansson <[email protected]>wrote: > Hi all, > > Would anyone mind if I go ahead and change all the Bus classes to Crossbar > or Xbar? > > Thus: > > Bus -> Xbar > CoherentBus -> CoherentXbar > NonCoherentBus -> NoncoherentXbar > > The current name is rather misleading as the interconnect is truly a > non-blocking crossbar (with separate multiplexers for the request, > response, snoop request and snoop response). > > Thanks, > > Andreas > > > -- IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > > ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, > Registered in England & Wales, Company No: 2557590 > ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, > Registered in England & Wales, Company No: 2548782 > _______________________________________________ > gem5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/gem5-dev > _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
