> On May 8, 2013, 12:44 p.m., Nilay Vaish wrote:
> > IIRC, you had previously stated that a multi-layered bus means that the bus 
> > has multiple
> > virtual channels that are multiplexed on to the same physical channel. The 
> > description 
> > of this patch seems to imply that layers are actually different physical 
> > channels.
> 
> Andreas Hansson wrote:
>     I think the channel concept is a little bit odd in this context, and 
> cannot exactly remember the discussion you are referring to.
>     
>     A layer is essentially an arbitration point, i.e. a big mux, and we used 
> to have these muxes on the input to the bus (before this patch), and with 
> this patch they are on the outputs for each of the different types of 
> transactions.
>     
>     Sorry if there is any confusion about this. With this patch the bus is 
> truly multi-layered (i.e. a crossbar) in the conventional bus terminology.

Anyone got any comments on the bus patches before I push them out?


- Andreas


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://reviews.gem5.org/r/1838/#review4321
-----------------------------------------------------------


On April 22, 2013, 3:43 p.m., Andreas Hansson wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://reviews.gem5.org/r/1838/
> -----------------------------------------------------------
> 
> (Updated April 22, 2013, 3:43 p.m.)
> 
> 
> Review request for Default.
> 
> 
> Description
> -------
> 
> Changeset 9679:7e980b7d406c
> ---------------------------
> mem: Make the buses multi layered
> 
> This patch makes the buses multi layered, and effectively creates a
> crossbar structure with distributed contention ports at the
> destination ports. Before this patch, a bus could have a single
> request, response and snoop response in flight at any time, and with
> these changes there can be as many requests as connected slaves (bus
> master ports), and as many responses as connected masters (bus slave
> ports).
> 
> Together with address interleaving, this patch enables us to create
> high-throughput memory interconnects, e.g. 50+ GByte/s.
> 
> 
> Diffs
> -----
> 
>   src/mem/bus.hh c5b24e8ed428 
>   src/mem/bus.cc c5b24e8ed428 
>   src/mem/coherent_bus.hh c5b24e8ed428 
>   src/mem/coherent_bus.cc c5b24e8ed428 
>   src/mem/noncoherent_bus.hh c5b24e8ed428 
>   src/mem/noncoherent_bus.cc c5b24e8ed428 
> 
> Diff: http://reviews.gem5.org/r/1838/diff/
> 
> 
> Testing
> -------
> 
> All regressions passing after stats updates
> 
> 
> Thanks,
> 
> Andreas Hansson
> 
>

_______________________________________________
gem5-dev mailing list
[email protected]
http://m5sim.org/mailman/listinfo/gem5-dev

Reply via email to