Jump to content

Kelly Stevens

  • Content Count

  • Joined

  • Last visited

About Kelly Stevens

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Roman, David, thank you for your responses and guidance. I'll add "coroutine" to my terminology stash. In answer to the question Roman asked at the end of his post, my use case involves a supervisor farming out job IDs to workers. It doesn't matter which worker does which job, so I was stuffing all the jobs into a fifo and letting chance decide who ends up with what. I agree with you all that switching to a deterministic approach is wise. I've rewritten my "write by one, read by many" example to respect ports and provide a manager that arbitrates requests (following along with Dav
  2. Hello! My question is whether it is thread-safe to use multiple readers on a fifo. The "quick reference card" I found here indicates this is not allowed. However, I have a working code example with multiple readers that throws no errors and I haven't found any official documentation forbidding this. Here is my sample code that works. In a nutshell, all the consumers get a pointer directly to the fifo and no fifo port is used. #include <systemc.h> #include <iostream> class Consumer : public sc_module { public: sc_in<bool> clock_in; sc_fifo&
  • Create New...