> The goal of this parch is to allow VMs to use standard ring names regardless > of the names given to the rings by host environment. It applies to > configurations using ivshmem. > > With shared memory rings, all VMs share a single namespace for the rings. > However, a VM will typically expect to find its rings with a pre-determined > name (e.g. p1_rx, p1_tx) regardless of how it's deployed, inserted in a > service chain, or of which other VMs are deployed alongside it. Hence, it is > desirable to introduce a level of indirection where the host can set a mapping > from the actual ring names (e.g. dpdkr0_rx|tx with OVS) and the names that > will be visible in the VM. This patch provides a simple implementation of such > a mapping scheme. > > Since the mapping must be VM specific, the aliases are inserted into the > IVSHMEM metadata area by the host and the guest side uses thoses aliases > when doing rte_ring_lookup(). > > A new function, rte_ivshmem_add_ring_alias() is provided in > librte_ivshmem to populate alias entries in the host environment when > creating the per-VM metadata.
Don't have any objections to this RFC, looks sensible to me as a concept. So, provided the tests are passing, Acked-by: Anatoly Burakov <anatoly.burakov at intel.com>
