2016-08-04 17:00, :
> Hi Thomas,
>
> I'm going to develop a NFV based carrier system with SPP because it's able
> to chain VMs in high-performance and I think it might be the best solution
> for service function chaining. Without ivshmem, throuput between VMs is
> largely decreased. So we are
Hi Thomas,
I'm going to develop a NFV based carrier system with SPP because it's able
to chain VMs in high-performance and I think it might be the best solution
for service function chaining. Without ivshmem, throuput between VMs is
largely decreased. So we are not so happy if ivshmem is obsoleted
> > There was a prior call with an explanation of what needs to be done:
> > http://dpdk.org/ml/archives/dev/2016-June/040844.html
> > - Qemu patch upstreamed
> > - IVSHMEM PCI device managed by a PCI driver
> > - No DPDK objects (ring/mempool) allocated by EAL
> >
> > As nobody seems inter
On Wed, Jul 20, 2016 at 6:35 PM, Thomas Monjalon
wrote:
> There was a prior call with an explanation of what needs to be done:
> http://dpdk.org/ml/archives/dev/2016-June/040844.html
> - Qemu patch upstreamed
> - IVSHMEM PCI device managed by a PCI driver
> - No DPDK objects (ring/mempool)
2016-07-22 00:36, Hiroshi Shimamoto:
> Hi,
>
> > Subject: [dpdk-dev] [PATCH] doc: announce ivshmem support removal
> >
> > There was a prior call with an explanation of what needs to be done:
> > http://dpdk.org/ml/archives/dev/2016-June/040844.html
> > -
Hi,
> Subject: [dpdk-dev] [PATCH] doc: announce ivshmem support removal
>
> There was a prior call with an explanation of what needs to be done:
> http://dpdk.org/ml/archives/dev/2016-June/040844.html
> - Qemu patch upstreamed
> - IVSHMEM PCI device managed by a PCI
There was a prior call with an explanation of what needs to be done:
http://dpdk.org/ml/archives/dev/2016-June/040844.html
- Qemu patch upstreamed
- IVSHMEM PCI device managed by a PCI driver
- No DPDK objects (ring/mempool) allocated by EAL
As nobody seems interested, it is time to remove
7 matches
Mail list logo
