Nilay Vaish 7a0d5aafe4 ruby: message buffers: significant changes ... This patch is the final patch in a series of patches. The aim of the series is to make ruby more configurable than it was. More specifically, the connections between controllers are not at all possible (unless one is ready to make significant changes to the coherence protocol). Moreover the buffers themselves are magically connected to the network inside the slicc code. These connections are not part of the configuration file. This patch makes changes so that these connections will now be made in the python configuration files associated with the protocols. This requires each state machine to expose the message buffers it uses for input and output. So, the patch makes these buffers configurable members of the machines. The patch drops the slicc code that usd to connect these buffers to the network. Now these buffers are exposed to the python configuration system as Master and Slave ports. In the configuration files, any master port can be connected any slave port. The file pyobject.cc has been modified to take care of allocating the actual message buffer. This is inline with how other port connections work.		2014-09-01 16:55:47 -05:00
..
MESI_Three_Level.py	ruby: message buffers: significant changes	2014-09-01 16:55:47 -05:00
MESI_Two_Level.py	ruby: message buffers: significant changes	2014-09-01 16:55:47 -05:00
MI_example.py	ruby: message buffers: significant changes	2014-09-01 16:55:47 -05:00
MOESI_CMP_directory.py	ruby: message buffers: significant changes	2014-09-01 16:55:47 -05:00
MOESI_CMP_token.py	ruby: message buffers: significant changes	2014-09-01 16:55:47 -05:00
MOESI_hammer.py	ruby: message buffers: significant changes	2014-09-01 16:55:47 -05:00
Network_test.py	ruby: message buffers: significant changes	2014-09-01 16:55:47 -05:00
Ruby.py	ruby: message buffers: significant changes	2014-09-01 16:55:47 -05:00