Re: [gem5-users] Ruby Message.clone() -- multicast

Thanks for the advice, Tushar. I think deleting it is fine; its a reference counted pointer (or so it appears to be), so it won't actually be deleted until all references have been cleared. At any rate, I did just go ahead and attach an extra id to the flits. Not terrible. Thanks! -Mark On Tue

Re: [gem5-users] Ruby Message.clone() -- multicast

Do you know http://code.google.com/p/tpzsimul/? It support multicast and much accurate router models than Garnet --Valentin El 08/08/2012, a las 00:27, Mark Browning escribió: > Is it generally safe to send multiple copies of the same > MsgPointer(ref-counted) around? That is, if a message

Re: [gem5-users] Ruby Message.clone() -- multicast

Hi Mark, No sending the same MsgPointer around can cause problems because the NI that receives it earlier will send it up to the cache/dir controller which will delete it after consuming it. You could perhaps add some extra bcast_id in the message at the source and identify it based on the {sou

[gem5-users] Ruby Message.clone() -- multicast

Is it generally safe to send multiple copies of the same MsgPointer(ref-counted) around? That is, if a message has multiple destinations and it arrives at one, will that destination modify the underlying Message in a way which will affect other destinations? Garnet doesn't support multi/broadcasti