• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 97 subscribers
  • Views 182 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Does an IHeapMP exist in IPC?

Nick Borton
Genius 3595 points

I would like to decouple the opener of a Multi Processor capable heap from knowing which type of heap it is openning (Mem, Buf, MultiBuf), I would like it to just have to know the name. Does an interface multiprocessor heap exist for this purpose?

Thanks

  • 0
    TI__Mastermind 32475 points

    No, there's no such IHeapMP interface.

    What's the motivation for such an interface?

    Judah

  • 0 in reply to judahvang
    Genius 3595 points

    The motivation behind this is to separate the heap details from one core design to another. I have been following some rules in that the creator of a messageq also creates the heap. Now the openner does not need to know what type of heap was created. The openner just needs to open the heap and register it with messageq, which only needs an IHeap handle. With an IHeapMP type, the creator of the heap is the only one who needs to know whether it is a Mem, Buf, or Multibuf. The openner could just use the IHeapMP type to get access to the open method. With the way I am currently designing my task modules, both sides need to know what type of heap the other is using. This makes part of the XDC Module idea less flexible, since others down the line cannot just mix and match modules.

    Ideally, I just want to have a global App.xs, which I loadCapsule with. This App.xs contains just the names of the heaps, and messageqs used by that app. Each core's config file passes the names out of the capsule into each module. The rest would be transparent. No need for both sides to know what heaps are being used.