DPDK usage discussions
 help / color / Atom feed
* [dpdk-users] examples/ip_reassembly - lcore per port
@ 2020-06-04  6:41 Saar Tarnopolsky
  0 siblings, 0 replies; only message in thread
From: Saar Tarnopolsky @ 2020-06-04  6:41 UTC (permalink / raw)
  To: users

Hi,

I am using the dpdk ip_reassambly code to reassemble fragmented packets sent to my Mellanox ConnectX-5.
While running the code I noticed that I can only run with one lcore per port. After reviewing the ip_reassembly code I saw that the code is built to initialize only lcore per port.
Is this a bug in the code?
Is there any way to run the ip_reassembly with more than one lcore per port? Or do I need to make my own modifications to the code to be able to tun it this way?

I run this command: ./build/ip_reassembly -l 0-3 -w 03:00.0 -- -p 0x1

And I get the following messages:
EAL: Detected 16 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: 1024 hugepages of size 2097152 reserved, but no mounted hugetlbfs found for that size
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: PCI device 0000:03:00.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 15b3:a2d2 net_mlx5
net_mlx5: DV flow is not supported
IP_RSMBL: Creating LPM table on socket 0
IP_RSMBL: Creating LPM6 table on socket 0
USER1: rte_ip_frag_table_create: allocated of 25165952 bytes at socket 0
nb_mbuf: 165888
Initializing port 0 ...  Address:98:03:9B:93:8D:76
txq=0,0,0 txq=1,1,0 txq=2,2,0 txq=3,3,0

IP_RSMBL: Socket 0: adding route 100.10.0.0/16 (port 0)
IP_RSMBL: Socket 0: adding route 100.20.0.0/16 (port 1)
IP_RSMBL: Socket 0: adding route 100.30.0.0/16 (port 2)
IP_RSMBL: Socket 0: adding route 100.40.0.0/16 (port 3)
IP_RSMBL: Socket 0: adding route 100.50.0.0/16 (port 4)
IP_RSMBL: Socket 0: adding route 100.60.0.0/16 (port 5)
IP_RSMBL: Socket 0: adding route 100.70.0.0/16 (port 6)
IP_RSMBL: Socket 0: adding route 100.80.0.0/16 (port 7)
IP_RSMBL: Socket 0: adding route 0101:0101:0101:0101:0101:0101:0101:0101/48 (port 0)
IP_RSMBL: Socket 0: adding route 0201:0101:0101:0101:0101:0101:0101:0101/48 (port 1)
IP_RSMBL: Socket 0: adding route 0301:0101:0101:0101:0101:0101:0101:0101/48 (port 2)
IP_RSMBL: Socket 0: adding route 0401:0101:0101:0101:0101:0101:0101:0101/48 (port 3)
IP_RSMBL: Socket 0: adding route 0501:0101:0101:0101:0101:0101:0101:0101/48 (port 4)
IP_RSMBL: Socket 0: adding route 0601:0101:0101:0101:0101:0101:0101:0101/48 (port 5)
IP_RSMBL: Socket 0: adding route 0701:0101:0101:0101:0101:0101:0101:0101/48 (port 6)
IP_RSMBL: Socket 0: adding route 0801:0101:0101:0101:0101:0101:0101:0101/48 (port 7)

Checking link status
done
Port0 Link Up. Speed 100000 Mbps - full-duplex
IP_RSMBL: lcore 1 has nothing to do
IP_RSMBL: lcore 2 has nothing to do
IP_RSMBL: lcore 3 has nothing to do
IP_RSMBL: entering main loop on lcore 0
IP_RSMBL:  -- lcoreid=0 portid=0

Thanks,
Saar

^ 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 --
2020-06-04  6:41 [dpdk-users] examples/ip_reassembly - lcore per port Saar Tarnopolsky

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