To illustrate the TAP port usage, the sample configuration file with
passthrough pipeline connected to TAP interface is added.
Signed-off-by: Jasvinder Singh
Acked-by: Cristian Dumitrescu
---
examples/ip_pipeline/config/tap.cfg | 64 +
1 file changed, 64
The TAP port support is added to ip_pipeline app. To parse
configuration file with TAP port entries, parsing function is implemented.
The TAP ports configuration check and initialization routines have been
included in application code.
Signed-off-by: Jasvinder Singh
Acked-by: Cristian Dumitrescu
This patch adds File Descriptor(FD) port type (e.g. TAP port) to the
packet framework library that allows interface with the kernel network
stack. The FD port APIs are defined that allow port creation, writing
and reading packet from the kernel interface.
Signed-off-by: Jasvinder Singh
Acked-by:
Hello,
Well, I see another problem here. I do not use rte_eth_driver_register
function at all, because my device is pure virtual. When I was writting
my own PMD, I used pcap PMD and null PMD as a starting point.
Best regards
On 04.09.2016 09:15, Eli Britstein wrote:
> Hi
>
> In your PMD, you
I know RedHat is working on a vIOMMU so I guess this work is related to
that effort, but it is a surprise virtio using IOMMU. I thought IOMMU just
made sense when using SRIOV. My second guess is using IOMMU with virtio is
a matter of security, but by other hand, virtio + IOMMU could imply serious
Hi
In your PMD, you should mark your init function as constructor, in which you
should register your PMD as a DPDK driver.
You can look at Intel's "memnic" example (though not maintained, and not being
compiled with recent versions, you can take it as a reference).
The function I mean from it:
6 matches
Mail list logo
