This patch enables the client dpdk rings within the netdev-dpdk. It adds
a new
dpdk device called dpdkr (other naming suggestions?). This allows for the
use
of shared memory to communicate with other dpdk applications, on the host
or
within a virtual machine. Instructions for use are in INSTALL.
Pravin,
On the 1GB page question. The patch simply allocates the rings and
creates a port. You can allocate more than a single 1 GB page, the
restriction is that it would need 1GB pages. The entire Huge Page
allocated by DPDK is passed to each Virtual Machine, and all VM¹s share
this memory. T
Pravin Shelar wrote:
>> On Wed, May 7, 2014 at 8:49 AM, Rogers, Gerald
>> wrote:
>> > As for the formatting issues, is there a ??c?? pretty print formatter
>>I can
>> > run on ovs_client.c to make it conform to coding standards?
>>
>> I do not know such
Pravin,
Which version of DPDK are you using?
In mine the rte_config.h is located in the DPDK directory
include/rte_config.h
Gerald
On 6/24/14, 12:11 PM, "Pravin Shelar" wrote:
>Hi Gerald,
>
>Thanks for updating patch, here are few comments:
>
>I got compilation erorr without --with-dpdk confi
t;headers.
>
>On Tue, Jun 24, 2014 at 07:29:29PM +, Rogers, Gerald wrote:
>> Pravin,
>>
>> Which version of DPDK are you using?
>>
>> In mine the rte_config.h is located in the DPDK directory
>> include/rte_config.h
>>
>> Gerald
>
Pravin,
There are some deployments that are using or require older OS
distributions using qemu versions prior to version 2.1, thus would require
the support for vHost-cuse. Most general reason is qualification cycles
for new OS versions. The patch provides compile time support for choosing
which
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
