[dpdk-dev] [PATCH] dropping librte_ivshmem - was log: deprecate history dump

2016-06-21 Thread Panu Matilainen
On 06/10/2016 12:26 AM, Thomas Monjalon wrote: > Looking a bit more into librte_ivshmem, the documentation says we need > a Qemu patch but the URL doesn't exist anymore: > https://01.org/packet-processing/intel%C2%AE-ovdk > -> 404 Oops, we couldn't find that page > > I've never understo

[dpdk-dev] [PATCH] dropping librte_ivshmem - was log: deprecate history dump

2016-06-15 Thread Ferruh Yigit
On 6/9/2016 10:26 PM, Thomas Monjalon wrote: > Looking a bit more into librte_ivshmem, the documentation says we need > a Qemu patch but the URL doesn't exist anymore: > https://01.org/packet-processing/intel%C2%AE-ovdk > -> 404 Oops, we couldn't find that page > > I've never understoo

[dpdk-dev] [PATCH] dropping librte_ivshmem - was log: deprecate history dump

2016-06-10 Thread Thomas Monjalon
2016-06-10 12:08, Burakov, Anatoly: > Hi Thomas, > > > 2016-06-10 09:47, Burakov, Anatoly: > > > > > > The last step of the ivshmem cleanup will be to remove the > > > > > > memory hack RTE_EAL_SINGLE_FILE_SEGMENTS. Then > > > > > > CONFIG_RTE_LIBRTE_IVSHMEM could be removed. > > > > > > > > > >

[dpdk-dev] [PATCH] dropping librte_ivshmem - was log: deprecate history dump

2016-06-10 Thread Thomas Monjalon
2016-06-10 09:47, Burakov, Anatoly: > > > > The last step of the ivshmem cleanup will be to remove the memory > > > > hack RTE_EAL_SINGLE_FILE_SEGMENTS. Then CONFIG_RTE_LIBRTE_IVSHMEM > > > > could be removed. > > > > > > The reason for that hack is that we often need to map several hugepages, > >

[dpdk-dev] [PATCH] dropping librte_ivshmem - was log: deprecate history dump

2016-06-10 Thread Burakov, Anatoly
Hi Thomas, > 2016-06-10 09:47, Burakov, Anatoly: > > > > > The last step of the ivshmem cleanup will be to remove the > > > > > memory hack RTE_EAL_SINGLE_FILE_SEGMENTS. Then > > > > > CONFIG_RTE_LIBRTE_IVSHMEM could be removed. > > > > > > > > The reason for that hack is that we often need to ma

[dpdk-dev] [PATCH] dropping librte_ivshmem - was log: deprecate history dump

2016-06-10 Thread Burakov, Anatoly
> > Hi Thomas, > > > > Just a few notes: > > > > > 3/ The automatic mapped allocation of DPDK objects in the guest. > > > It should not be done in EAL. > > > An ivshmem driver would be called by rte_eal_dev_init. > > > It would check where are the shared DPDK structures, as currently > > > done wit

[dpdk-dev] [PATCH] dropping librte_ivshmem - was log: deprecate history dump

2016-06-10 Thread Burakov, Anatoly
Hi Thomas, Just a few notes: > 3/ The automatic mapped allocation of DPDK objects in the guest. > It should not be done in EAL. > An ivshmem driver would be called by rte_eal_dev_init. > It would check where are the shared DPDK structures, as currently done with > the IVSHMEM_MAGIC (0x0BADC0DE),

[dpdk-dev] [PATCH] dropping librte_ivshmem - was log: deprecate history dump

2016-06-10 Thread Thomas Monjalon
2016-06-10 09:05, Burakov, Anatoly: > Hi Thomas, > > Just a few notes: > > > 3/ The automatic mapped allocation of DPDK objects in the guest. > > It should not be done in EAL. > > An ivshmem driver would be called by rte_eal_dev_init. > > It would check where are the shared DPDK structures, as cu

[dpdk-dev] [PATCH] dropping librte_ivshmem - was log: deprecate history dump

2016-06-09 Thread Thomas Monjalon
Looking a bit more into librte_ivshmem, the documentation says we need a Qemu patch but the URL doesn't exist anymore: https://01.org/packet-processing/intel%C2%AE-ovdk -> 404 Oops, we couldn't find that page I've never understood why we should keep this wart and now I'm going to b