Proposal for Creating Shared Memory Areas via a Character Device

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear Mr. Dickins,

We have identified certain scenarios, such as interactions between running Docker containers and their hosts, where there is currently no suitable method to efficiently create shared memory areas. This limitation arises due to the isolated nature of these environments and the assumption that necessary path mappings may not have been configured during Docker startup.

My proposal involves introducing a character device driver (e.g., /dev/shared-mem) that allows processes within Docker containers and on the host system to share memory via mmap operations on this device. Unlike alternative solutions such as mmap-ing through file paths, this method eliminates the need to restart Docker containers by enabling Docker to access a specific character driver.

Thank you for considering this proposal, which aims to facilitate efficient data exchange between Docker containers and their hosts without disrupting ongoing operations.

Looking forward to hearing from you.

Best regards,

Manny Wang


[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux