On 10/5/2018 9:57 AM, Burakov, Anatoly wrote:
> On 03-Oct-18 1:39 PM, Darek Stojaczyk wrote:
>> So far each process in MP used to have a separate container
>> and relied on the primary process to register all memsegs.
>>
>> Mapping external memory via rte_vfio_container_dma_map()
>> in secondary pr
> -Original Message-
> From: Burakov, Anatoly
> Sent: Friday, October 5, 2018 10:58 AM
>
> > + if (internal_config.process_type == RTE_PROC_PRIMARY) {
> > + /* if we were secondary process we would try requesting
> > +* container fd from the primary, but we're
On 03-Oct-18 1:39 PM, Darek Stojaczyk wrote:
So far each process in MP used to have a separate container
and relied on the primary process to register all memsegs.
Mapping external memory via rte_vfio_container_dma_map()
in secondary processes was broken, because the default
(process-local) cont
On 04-Oct-18 4:52 PM, Burakov, Anatoly wrote:
On 03-Oct-18 1:39 PM, Darek Stojaczyk wrote:
So far each process in MP used to have a separate container
and relied on the primary process to register all memsegs.
Mapping external memory via rte_vfio_container_dma_map()
in secondary processes was b
On 03-Oct-18 1:39 PM, Darek Stojaczyk wrote:
So far each process in MP used to have a separate container
and relied on the primary process to register all memsegs.
Mapping external memory via rte_vfio_container_dma_map()
in secondary processes was broken, because the default
(process-local) cont
So far each process in MP used to have a separate container
and relied on the primary process to register all memsegs.
Mapping external memory via rte_vfio_container_dma_map()
in secondary processes was broken, because the default
(process-local) container had no groups bound. There was
even no wa
6 matches
Mail list logo
