DPDK usage discussions
 help / color / Atom feed
* [dpdk-users] Route packets to DPDK interface or setup Bifurcated Flow
@ 2019-08-13 15:57 Andrew Wang
  0 siblings, 0 replies; only message in thread
From: Andrew Wang @ 2019-08-13 15:57 UTC (permalink / raw)
  To: users

Hi


We have the following setup: a linux box running Ubuntu 18.04 with 2
interfaces, one controlled by the kernel (eno49), from which we receive
incoming packets from the switch, and another interface (eno50), which is
taken over by our DPDK app, and would ideally only process packets coming
from eno49 for a specific IPv6 subnet and forward them to the backend
server. See the schematic below:



+-------------+

|   Switch    |

+-------------+

    |

    |

+---+---------+

|    eno49    |  eno49 - interface controlled by kernel

|             |

|    eno50    |  eno50 - interface taken over by DPDK

+---+---------+

    |

    |

+-------------+

|    Backend  |

+-------------+



However, when the DPDK app takes over the interface, we can no longer see
the interface via commands like "ip link show". So it seems we can no
longer set commands like "ip -6 route add <IPv6 subnet> dev eno50`. Our
DPDK app currently does not implement Neighbor Discovery Protocol so we
cannot set route via an IPv6 address. Is there a way of forwarding incoming
packets from eno49 to our eno50 interface?


We tried setting up flow bifurcation, but got the following error:


# dmesg |grep Virtualization

[    1.537848] DMAR: Intel(R) Virtualization Technology for Directed I/O


# cat /proc/cmdline

BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic
root=UUID=023bc8a4-513f-4ddb-977e-9e49ea2f8477 ro maybe-ubiquity
default_hugepagesz=1G hugepagesz=1G hugepages=4 intel_iommu=on iommu=pt


# cat /sys/bus/pci/devices/0000:04:00.1/sriov_numvfs

2


# ip link show enp4s16f1

15: enp4s16f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode
DEFAULT group default qlen 1000

    link/ether 2a:82:46:01:0d:ce brd ff:ff:ff:ff:ff:ff


# ip link show eno50

7: eno50: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode
DEFAULT group default qlen 1000

    link/ether 5c:b9:01:98:7f:d5 brd ff:ff:ff:ff:ff:ff

    vf 0 MAC 2a:82:46:01:0d:ce, spoof checking on, link-state auto, trust
off, query_rss off

    vf 1 MAC 72:bc:92:d8:81:75, spoof checking on, link-state auto, trust
off, query_rss off


# ethtool -i enp4s16f1

driver: ixgbevf

version: 4.6.1

firmware-version:

expansion-rom-version:

bus-info: 0000:04:10.1

supports-statistics: yes

supports-test: yes

supports-eeprom-access: no

supports-register-dump: yes

supports-priv-flags: yes


# ethtool -K enp4s16f1 ntuple on

Cannot change ntuple-filters

Could not change any device features


Any suggestions on how we can proceed? Either help with directing flow or
getting flow bifurcation to work would be highly appreciated.


Thanks in advance

Andrew

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, back to index

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-08-13 15:57 [dpdk-users] Route packets to DPDK interface or setup Bifurcated Flow Andrew Wang

DPDK usage discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ http://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/ public-inbox