Bruce, Stephen,
It may be a duplicate, but people are likely using it. I would assume
deprecate means don?t remove, but put in a comment that says please don?t
use and migrate your code away from it.
Thanks,
Gerald
On 6/23/14, 3:18 PM, "Richardson, Bruce"
wrote:
>> -Original Message-
Venky,
This also applies to mbuf pools. Inside of the openvswitch.org patches we
allocate mbuf pools for a port, but we are unable to free them back when
the port is removed.
One other request (maybe it is there, and I?m unaware), is the ability to
dynamically add / remove a physical port to DPD
Etai,
If this doesn?t work, then you will need to change the virtual address
range that is used by DPDK. By default this is set dynamically, however;
with DPDK 1.6you can change it to any region in the virtual address space
you want.
The problem you have is what you stated, the secondary process
Palin,
Support for the i217 will be available in the Intel DPDK version 1.7. I?m
not sure of the timeline, but next release.
Gerald
On 1/30/14, 10:59 AM, "Palin, Francois"
wrote:
>Hi all,
>
>We would like to know if DPDK support for the i217 will be provided
>anytime soon.
>The Supported NICs
Prashant,
IVShm is supported by the Intel DPDK client rings, and a patched QEMU/KVM
from the OVDK work on 01.org (https://01.org/packet-processing). The main
part being the patched QEMU/KVM to map the Intel DPDK Huge Page Tables
(with Release of Intel DPDK 1.6 the requirement to map 1 GB huge pag
5 matches
Mail list logo