-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MulticastRoutingTableByPartitionEntry needs a Spin2 version #549
Comments
I thought the actual bits were part of SpiNNMachine. Maybe this should be the case if it isn't already... |
There are hard coded n_cores, shifts and masks PACMAN/pacman/model/routing_table_by_partition/multicast_routing_table_by_partition_entry.py Line 23 in 07ec798
The big issue is that many changes here(python side) need matching changes C side |
If this is PACMAN or SpiNNMachine is the least of the worries here |
It is more a case of having lots of different places that do the same thing. In some ways, it would be useful for PACMAN to "not care" about the details of SpiNNaker bits, and just ask SpiNNMachine to do it. There is a MulticastRoutingEntry in SpiNNMachine, so maybe this is a better place to do conversions? In terms of things happening in C, only SCAMP / SARK would need to be different. Nowhere else should care... |
The relationship between Pacman's MulticastRoutingTableByPartitionEntry and SpinnMachine's MulticastRoutingEntry does need reviewing. Why have 2 and why does the PACMAN one have and need incoming info. |
fixed by #550 |
MulticastRoutingTableByPartitionEntry its spinnaker_route uses 5 bits for processor id.
It appears that the first 8 ant last 8 bits are used.
3 for link and 5 for processors.
5 bits are not enough for all the spin cores.
===
For spin2 we will need to decide if the cores are virtual or 2d addresses
The text was updated successfully, but these errors were encountered: