Skip to content
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

Is shared memory no longer supported? #1883

Closed
ex-purple opened this issue Nov 20, 2023 · 3 comments
Closed

Is shared memory no longer supported? #1883

ex-purple opened this issue Nov 20, 2023 · 3 comments
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@ex-purple
Copy link

ex-purple commented Nov 20, 2023

Hi there,
I have a problem with shared memory usage on master:
config: //CycloneDDS/Domain/SharedMemory: 'Enable': deprecated element
config: //CycloneDDS/Domain/SharedMemory: 'LogLevel': deprecated element

Is shared memory no longer supported? Or maybe this documentation is deprecated?

@eboasson
Copy link
Contributor

Oops. The documentation is outdated.

The code for integrating Iceoryx used to be "hard-coded", with references to Iceoryx in various place in the Cyclone sources. We refactored it out into a plugin-based mechanism (see #1676) and added a plugin for Iceoryx in the sources. The "correct" way of configuring now looks like:

<General>
  <Interfaces>
    <PubSubMessageExchange name="iox" library="psmx_iox" config="LOG_LEVEL=INFO;"/>
  </Interfaces>
</General>

The old settings continue to work with a warning. They just translate the old (unchanging) configuration to the new format so they'll probably be around for quite some time.

@eboasson eboasson added documentation Improvements or additions to documentation bug Something isn't working labels Nov 28, 2023
@ciandonovan
Copy link

Are there plans to use this new plugin interface to provide other shared-memory providers beside Iceoryx? Maybe a daemon-less one, similar to what FastDDS does? Use the loopback just for discovery, handshakes, etc. before coordinating on the shared-memory segment to use? Have had issues with Iceoryx crashing with a large amount of nodes, would be nice if there wasn't a single point of failure as currently everything must be restarted if Iceoryx crashes AFAIK.

@eboasson
Copy link
Contributor

@ciandonovan There are a few rough edges around that plug-in interface as it is stands today, but in principle, yes, the idea is that this will become a proper interface. That then gives way more freedom to use alternative ways of doing shared memory (or other pub/sub systems).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants