Communication CFT Weekly [2025-01-20]

[qor-lb]

Participants

• Lars Bauhofer @qor-lb
• Armin Bartsch @armin-acn
• Markus Bechter @ramceb
• Oliver Emrich
• Jochen Hönle @hoe-jo
• Martin Mössmer
• Nico Hartmann @HartmannNico
• Danial Norouzi Seyed
• Thilo Schmitt @thilo-schmitt
• Frank Scholter Peres @FScholPer
• Arvid Sievert @arsibo
• Martin Thiede @mthiede-acn2
• Vinod Reddy Gopi Reddy @vinodreddy-g

Agenda

1. Welcome & Introduction
2. Work mode
3. Goal/Vision
4. Next Steps

Meeting Minutes

to 2.

• Goal: Decision mid of February for the Communication Framework
• Approach:
  1. Rough roadmap for the feature until end of June
  2. Harmonize feature request
  3. Evaluate the existing contribution concepts
  4. Decision for feature basis moving ahead
• Existing Contributions to be considered until now
  • LoLa
  • IceOryx

to 3.

• Should the communication framework also be the interface for application communication in the FEO Framework?
  • The application framework might have specializations to improve performance in specific scenarios, however, this "additional layer" should operate on top of this communication framework
• List of intended target OSs

to 4.

• Review feature request until "Names" section within PR IPC Contribution Request Initial Version #85 (further reviews are allowed)

[LittleHuba]

Two things I noted down during the meeting, missing in above notes:

to 3. Additional info from the meeting:

Motivation for highly efficient local communication (IPC with zero copy):

• Mixed criticality
• Mixed domains

Supported communication (wishlist):

• IPC
• Inter-OS
• Inter-Container
• Inter-Chip (DMA?)

Nico Hartmann: "Some kind of memory-like access with layouted data which is accessible from sender and receiver"

[alex-warg-mb]

We should make sure if access control underlying communication is in scope. I currently miss that topic in eCAL, iceoryx etc.