Hi Pavlos, That¹s right. In the NonCoherentBus, for every connected slave, there is a multiplexer (layer) for the incoming requests. For every connected master, there is a multiplexer (layer) for the incoming responses.
In the case of the CoherentBus, snoop requests are never waiting/contending. Snoop responses converge at the connected slaves, and thus for every connected slave there is a multiplexer (layer) for the snoop responses. Andreas On 10/06/2014 17:00, "Pavlos Maniotis via gem5-dev" <[email protected]> wrote: >Thank you for making it clear. So, taking as an example the coherent bus >is >it like the configuration in the following image with three layers (1 for >requests, 1 for snoops and 1 for responses)? > >http://www.doulos.com/knowhow/arm/Migrating_from_AHB_to_AXI/multilayer_bus >_simple.png > >Thanks again, >Pavlos > > >On Tue, Jun 10, 2014 at 5:55 PM, Andreas Hansson via gem5-dev < >[email protected]> wrote: > >> Hi Pavlos, >> >> It is a crossbar implemented by muxes. >> >> I am in the process of renaming the class XBar (from Bus) to avoid any >> confusion. >> >> Andreas >> >> On 10/06/2014 15:50, "Pavlos Maniotis via gem5-dev" <[email protected]> >> wrote: >> >> >Hello everyone, >> > >> >I have read the following thread and I feel that I have not completely >> >understood what is the actual configuration for the CoherentBus (and >> >generally the Bus) model. >> > >> >https://www.mail-archive.com/[email protected]/msg10942.html >> > >> > >> >Is it just a shared medium between the master and slave ports similarly >> >to the example in the following link's image or is it a crossbar? >> > >> > >> >>http://upload.wikimedia.org/wikipedia/commons/thumb/6/68/Computer_system_ >>b >> >us.svg/744px-Computer_system_bus.svg.png >> > >> >It would be nice if someone could provide a graphical representation of >> >how the master and slave ports are actually connected by utilizing the >> >bus modules (coherent or non-coherent, I assume it is the same for both >> >of them). >> > >> >Thank you in advance for your help, >> >Pavlos >> > >> >_______________________________________________ >> >gem5-dev mailing list >> >[email protected] >> >http://m5sim.org/mailman/listinfo/gem5-dev >> > >> >> >> -- 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 > -- 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
