[dpdk-dev] Running DPDK application without non-previlege mode

[dpdk-dev] Running DPDK application without non-previlege mode

[Kamaraj P]

Hello All,

We are not able to run the DPDK allocation without using privilege option.

Able to see the below erors:

set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
EAL: FATAL: rte_service_init() failed
Failed to init DPDK.set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
Failed to create mbuf for pool DPDK_POOL_0 frame_len=2048 num_mbufs=13824
ret (Exec format error)

BTW we are also enabling --iova-mode=va option as part DPDK init.

Can anyone please throw some light on this ?

Thanks,
Kamaraj

Re: [dpdk-dev] Running DPDK application with non-previlege mode

[Kamaraj P]

Hello All,
Some more info.
We are using DPDK 19.11.

When we bringup application with --security-opt seccomp=unconfined
option..
THe application bringup successfully and didnt observe any error when DPDK
init logs.
Will that --security-opt seccomp=unconfined option recommended for
non-previlege mode for DPDK application ?
Please suggest.

Thanks,
Kamaraj

On Mon, Aug 30, 2021 at 1:07 PM Kamaraj P <pkamaraj@gmail.com> wrote:

> Hello All,
>
> We are not able to run the DPDK allocation without using privilege option.
>
> Able to see the below erors:
>
> set_mempolicy: Operation not permitted
> set_mempolicy: Operation not permitted
> set_mempolicy: Operation not permitted
> set_mempolicy: Operation not permitted
> set_mempolicy: Operation not permitted
> set_mempolicy: Operation not permitted
> set_mempolicy: Operation not permitted
> set_mempolicy: Operation not permitted
> EAL: FATAL: rte_service_init() failed
> Failed to init DPDK.set_mempolicy: Operation not permitted
> set_mempolicy: Operation not permitted
> set_mempolicy: Operation not permitted
> set_mempolicy: Operation not permitted
> set_mempolicy: Operation not permitted
> set_mempolicy: Operation not permitted
> set_mempolicy: Operation not permitted
> set_mempolicy: Operation not permitted
> Failed to create mbuf for pool DPDK_POOL_0 frame_len=2048 num_mbufs=13824
> ret (Exec format error)
>
> BTW we are also enabling --iova-mode=va option as part DPDK init.
>
> Can anyone please throw some light on this ?
>
> Thanks,
> Kamaraj
>

Re: [dpdk-dev] Running DPDK application with non-previlege mode

[Kamaraj P]

DPDK logs:

Used system capability: --cap-add=NET_ADMIN --cap-add=SYS_RESOURCE --rm -v
/dev:/dev to bring up the DPDK application

Enabling IOVA mode
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
EAL: FATAL: rte_service_init() failed
Failed to init DPDK.DPDL Display Logs 08-30-2021  08:28:50.335069 EAL:
Detected lcore 0 as core 0 on socket 0
08-30-2021  08:28:50.335177 EAL: Detected lcore 1 as core 1 on socket 0
08-30-2021  08:28:50.335234 EAL: Detected lcore 2 as core 2 on socket 0
08-30-2021  08:28:50.335288 EAL: Detected lcore 3 as core 3 on socket 0
08-30-2021  08:28:50.335342 EAL: Detected lcore 4 as core 4 on socket 0
08-30-2021  08:28:50.335395 EAL: Detected lcore 5 as core 5 on socket 0
08-30-2021  08:28:50.335448 EAL: Detected lcore 6 as core 8 on socket 0
08-30-2021  08:28:50.335517 EAL: Detected lcore 7 as core 9 on socket 0
08-30-2021  08:28:50.335579 EAL: Detected lcore 8 as core 10 on socket 0
08-30-2021  08:28:50.335632 EAL: Detected lcore 9 as core 11 on socket 0
08-30-2021  08:28:50.335684 EAL: Detected lcore 10 as core 12 on socket 0
08-30-2021  08:28:50.335739 EAL: Detected lcore 11 as core 13 on socket 0
08-30-2021  08:28:50.335808 EAL: Detected lcore 12 as core 16 on socket 0
08-30-2021  08:28:50.335861 EAL: Detected lcore 13 as core 17 on socket 0
08-30-2021  08:28:50.335916 EAL: Detected lcore 14 as core 18 on socket 0
08-30-2021  08:28:50.335969 EAL: Detected lcore 15 as core 19 on socket 0
08-30-2021  08:28:50.336020 EAL: Detected lcore 16 as core 20 on socket 0
08-30-2021  08:28:50.336072 EAL: Detected lcore 17 as core 21 on socket 0
08-30-2021  08:28:50.336123 EAL: Detected lcore 18 as core 24 on socket 0
08-30-2021  08:28:50.336174 EAL: Detected lcore 19 as core 25 on socket 0
08-30-2021  08:28:50.336242 EAL: Detected lcore 20 as core 26 on socket 0
08-30-2021  08:28:50.336296 EAL: Detected lcore 21 as core 27 on socket 0
08-30-2021  08:28:50.336350 EAL: Detected lcore 22 as core 28 on socket 0
08-30-2021  08:28:50.336401 EAL: Detected lcore 23 as core 29 on socket 0
08-30-2021  08:28:50.336462 EAL: Detected lcore 24 as core 0 on socket 1
08-30-2021  08:28:50.336522 EAL: Detected lcore 25 as core 1 on socket 1
08-30-2021  08:28:50.336580 EAL: Detected lcore 26 as core 2 on socket 1
08-30-2021  08:28:50.336638 EAL: Detected lcore 27 as core 3 on socket 1
08-30-2021  08:28:50.336697 EAL: Detected lcore 28 as core 4 on socket 1
08-30-2021  08:28:50.336756 EAL: Detected lcore 29 as core 5 on socket 1
08-30-2021  08:28:50.336824 EAL: Detected lcore 30 as core 8 on socket 1
08-30-2021  08:28:50.336883 EAL: Detected lcore 31 as core 9 on socket 1
08-30-2021  08:28:50.336941 EAL: Detected lcore 32 as core 10 on socket 1
08-30-2021  08:28:50.336999 EAL: Detected lcore 33 as core 11 on socket 1
08-30-2021  08:28:50.337073 EAL: Detected lcore 34 as core 12 on socket 1
08-30-2021  08:28:50.337132 EAL: Detected lcore 35 as core 13 on socket 1
08-30-2021  08:28:50.337189 EAL: Detected lcore 36 as core 16 on socket 1
08-30-2021  08:28:50.337248 EAL: Detected lcore 37 as core 17 on socket 1
08-30-2021  08:28:50.337306 EAL: Detected lcore 38 as core 18 on socket 1
08-30-2021  08:28:50.337368 EAL: Detected lcore 39 as core 19 on socket 1
08-30-2021  08:28:50.337426 EAL: Detected lcore 40 as core 20 on socket 1
08-30-2021  08:28:50.337484 EAL: Detected lcore 41 as core 21 on socket 1
08-30-2021  08:28:50.337541 EAL: Detected lcore 42 as core 24 on socket 1
08-30-2021  08:28:50.337598 EAL: Detected lcore 43 as core 25 on socket 1
08-30-2021  08:28:50.337656 EAL: Detected lcore 44 as core 26 on socket 1
08-30-2021  08:28:50.337713 EAL: Detected lcore 45 as core 27 on socket 1
08-30-2021  08:28:50.337771 EAL: Detected lcore 46 as core 28 on socket 1
08-30-2021  08:28:50.337848 EAL: Detected lcore 47 as core 29 on socket 1
08-30-2021  08:28:50.337900 EAL: Detected lcore 48 as core 0 on socket 0
08-30-2021  08:28:50.337951 EAL: Detected lcore 49 as core 1 on socket 0
08-30-2021  08:28:50.338003 EAL: Detected lcore 50 as core 2 on socket 0
08-30-2021  08:28:50.338058 EAL: Detected lcore 51 as core 3 on socket 0
08-30-2021  08:28:50.338110 EAL: Detected lcore 52 as core 4 on socket 0
08-30-2021  08:28:50.338161 EAL: Detected lcore 53 as core 5 on socket 0
08-30-2021  08:28:50.338216 EAL: Detected lcore 54 as core 8 on socket 0
08-30-2021  08:28:50.338267 EAL: Detected lcore 55 as core 9 on socket 0
08-30-2021  08:28:50.338343 EAL: Detected lcore 56 as core 10 on socket 0
08-30-2021  08:28:50.338398 EAL: Detected lcore 57 as core 11 on socket 0
08-30-2021  08:28:50.338450 EAL: Detected lcore 58 as core 12 on socket 0
08-30-2021  08:28:50.338502 EAL: Detected lcore 59 as core 13 on socket 0
08-30-2021  08:28:50.338569 EAL: Detected lcore 60 as core 16 on socket 0
08-30-2021  08:28:50.338621 EAL: Detected lcore 61 as core 17 on socket 0
08-30-2021  08:28:50.338671 EAL: Detected lcore 62 as core 18 on socket 0
08-30-2021  08:28:50.338722 EAL: Detected lcore 63 as core 19 on socket 0
08-30-2021  08:28:50.338774 EAL: Detected lcore 64 as core 20 on socket 0
08-30-2021  08:28:50.338825 EAL: Detected lcore 65 as core 21 on socket 0
08-30-2021  08:28:50.338876 EAL: Detected lcore 66 as core 24 on socket 0
08-30-2021  08:28:50.338928 EAL: Detected lcore 67 as core 25 on socket 0
08-30-2021  08:28:50.338981 EAL: Detected lcore 68 as core 26 on socket 0
08-30-2021  08:28:50.339033 EAL: Detected lcore 69 as core 27 on socket 0
08-30-2021  08:28:50.339085 EAL: Detected lcore 70 as core 28 on socket 0
08-30-2021  08:28:50.339137 EAL: Detected lcore 71 as core 29 on socket 0
08-30-2021  08:28:50.339199 EAL: Detected lcore 72 as core 0 on socket 1
08-30-2021  08:28:50.339273 EAL: Detected lcore 73 as core 1 on socket 1
08-30-2021  08:28:50.339331 EAL: Detected lcore 74 as core 2 on socket 1
08-30-2021  08:28:50.339389 EAL: Detected lcore 75 as core 3 on socket 1
08-30-2021  08:28:50.339447 EAL: Detected lcore 76 as core 4 on socket 1
08-30-2021  08:28:50.339507 EAL: Detected lcore 77 as core 5 on socket 1
08-30-2021  08:28:50.339566 EAL: Detected lcore 78 as core 8 on socket 1
08-30-2021  08:28:50.339623 EAL: Detected lcore 79 as core 9 on socket 1
08-30-2021  08:28:50.339682 EAL: Detected lcore 80 as core 10 on socket 1
08-30-2021  08:28:50.339740 EAL: Detected lcore 81 as core 11 on socket 1
08-30-2021  08:28:50.339806 EAL: Detected lcore 82 as core 12 on socket 1
08-30-2021  08:28:50.339865 EAL: Detected lcore 83 as core 13 on socket 1
08-30-2021  08:28:50.339925 EAL: Detected lcore 84 as core 16 on socket 1
08-30-2021  08:28:50.339985 EAL: Detected lcore 85 as core 17 on socket 1
08-30-2021  08:28:50.340046 EAL: Detected lcore 86 as core 18 on socket 1
08-30-2021  08:28:50.340120 EAL: Detected lcore 87 as core 19 on socket 1
08-30-2021  08:28:50.340178 EAL: Detected lcore 88 as core 20 on socket 1
08-30-2021  08:28:50.340236 EAL: Detected lcore 89 as core 21 on socket 1
08-30-2021  08:28:50.340293 EAL: Detected lcore 90 as core 24 on socket 1
08-30-2021  08:28:50.340351 EAL: Detected lcore 91 as core 25 on socket 1
08-30-2021  08:28:50.340410 EAL: Detected lcore 92 as core 26 on socket 1
08-30-2021  08:28:50.340467 EAL: Detected lcore 93 as core 27 on socket 1
08-30-2021  08:28:50.340532 EAL: Detected lcore 94 as core 28 on socket 1
08-30-2021  08:28:50.340591 EAL: Detected lcore 95 as core 29 on socket 1
08-30-2021  08:28:50.342259 EAL: Support maximum 128 logical core(s) by
configuration.
08-30-2021  08:28:50.342270 EAL: Detected 96 lcore(s)
08-30-2021  08:28:50.342297 EAL: Detected 2 NUMA nodes
08-30-2021  08:28:50.342404 EAL: open shared lib
/usr/lib64/dpdk-19/librte_pmd_ixgbe.so.20.0
08-30-2021  08:28:50.343232 EAL: open shared lib
/usr/lib64/dpdk-19/librte_pmd_e1000.so.20.0
08-30-2021  08:28:50.343711 EAL: open shared lib
/usr/lib64/dpdk-19/librte_pmd_bnxt.so.20.0
08-30-2021  08:28:50.345066 EAL: No shared files mode enabled, IPC will be
disabled
08-30-2021  08:28:50.345090 EAL: No shared files mode enabled, IPC is
disabled
08-30-2021  08:28:50.345116 EAL: No shared files mode enabled, IPC is
disabled
08-30-2021  08:28:50.345175 EAL: Module /sys/module/vfio_pci not found!
error 2 (No such file or directory)
08-30-2021  08:28:50.345187 EAL: VFIO PCI modules not loaded
08-30-2021  08:28:50.387521 EAL: Selected IOVA mode 'VA'
08-30-2021  08:28:50.387867 EAL: No available hugepages reported in
hugepages-1048576kB
08-30-2021  08:28:50.387874 EAL: In-memory mode enabled, hugepages of size
1073741824 bytes will be allocated anonymously
08-30-2021  08:28:50.387898 EAL: No free hugepages reported in
hugepages-1048576kB
08-30-2021  08:28:50.387915 EAL: No free hugepages reported in
hugepages-1048576kB
08-30-2021  08:28:50.387944 EAL: No available hugepages reported in
hugepages-1048576kB
08-30-2021  08:28:50.388145 EAL: Probing VFIO support...
08-30-2021  08:28:50.388157 EAL: Module /sys/module/vfio not found! error 2
(No such file or directory)
08-30-2021  08:28:50.388161 EAL: VFIO modules not loaded, skipping VFIO
support...
08-30-2021  08:28:50.388168 EAL: Ask a virtual area of 0x2e000 bytes
08-30-2021  08:28:50.388176 EAL: Virtual area found at 0x100000000 (size =
0x2e000)
08-30-2021  08:28:50.388296 EAL: Setting up physically contiguous memory...
08-30-2021  08:28:50.388309 EAL: Setting maximum number of open files to
1048576
08-30-2021  08:28:50.388314 EAL: Detected memory type: socket_id:0
hugepage_sz:1073741824
08-30-2021  08:28:50.388318 EAL: Detected memory type: socket_id:1
hugepage_sz:1073741824
08-30-2021  08:28:50.388322 EAL: Detected memory type: socket_id:0
hugepage_sz:2097152
08-30-2021  08:28:50.388325 EAL: Detected memory type: socket_id:1
hugepage_sz:2097152
08-30-2021  08:28:50.388329 EAL: Creating 4 segment lists: n_segs:32
socket_id:0 hugepage_sz:1073741824
08-30-2021  08:28:50.388333 EAL: Ask a virtual area of 0x1000 bytes
08-30-2021  08:28:50.388339 EAL: Virtual area found at 0x10002e000 (size =
0x1000)
08-30-2021  08:28:50.388347 EAL: Memseg list allocated: 0x100000kB at
socket 0
08-30-2021  08:28:50.388351 EAL: Ask a virtual area of 0x800000000 bytes
08-30-2021  08:28:50.388356 EAL: Virtual area found at 0x140000000 (size =
0x800000000)
08-30-2021  08:28:50.388363 EAL: Ask a virtual area of 0x1000 bytes
08-30-2021  08:28:50.388368 EAL: Virtual area found at 0x940000000 (size =
0x1000)
08-30-2021  08:28:50.388377 EAL: Memseg list allocated: 0x100000kB at
socket 0
08-30-2021  08:28:50.388381 EAL: Ask a virtual area of 0x800000000 bytes
08-30-2021  08:28:50.388386 EAL: Virtual area found at 0x980000000 (size =
0x800000000)
08-30-2021  08:28:50.388391 EAL: Ask a virtual area of 0x1000 bytes
08-30-2021  08:28:50.388396 EAL: Virtual area found at 0x1180000000 (size =
0x1000)
08-30-2021  08:28:50.388407 EAL: Memseg list allocated: 0x100000kB at
socket 0
08-30-2021  08:28:50.388411 EAL: Ask a virtual area of 0x800000000 bytes
08-30-2021  08:28:50.388415 EAL: Virtual area found at 0x11c0000000 (size =
0x800000000)
08-30-2021  08:28:50.388421 EAL: Ask a virtual area of 0x1000 bytes
08-30-2021  08:28:50.388425 EAL: Virtual area found at 0x19c0000000 (size =
0x1000)
08-30-2021  08:28:50.388434 EAL: Memseg list allocated: 0x100000kB at
socket 0
08-30-2021  08:28:50.388437 EAL: Ask a virtual area of 0x800000000 bytes
08-30-2021  08:28:50.388442 EAL: Virtual area found at 0x1a00000000 (size =
0x800000000)
08-30-2021  08:28:50.388447 EAL: Creating 4 segment lists: n_segs:32
socket_id:1 hugepage_sz:1073741824
08-30-2021  08:28:50.388451 EAL: Ask a virtual area of 0x1000 bytes
08-30-2021  08:28:50.388456 EAL: Virtual area found at 0x2200000000 (size =
0x1000)
08-30-2021  08:28:50.388464 EAL: Memseg list allocated: 0x100000kB at
socket 1
08-30-2021  08:28:50.388468 EAL: Ask a virtual area of 0x800000000 bytes
08-30-2021  08:28:50.388473 EAL: Virtual area found at 0x2240000000 (size =
0x800000000)
08-30-2021  08:28:50.388478 EAL: Ask a virtual area of 0x1000 bytes
08-30-2021  08:28:50.388482 EAL: Virtual area found at 0x2a40000000 (size =
0x1000)
08-30-2021  08:28:50.388492 EAL: Memseg list allocated: 0x100000kB at
socket 1
08-30-2021  08:28:50.388496 EAL: Ask a virtual area of 0x800000000 bytes
08-30-2021  08:28:50.388501 EAL: Virtual area found at 0x2a80000000 (size =
0x800000000)
08-30-2021  08:28:50.388506 EAL: Ask a virtual area of 0x1000 bytes
08-30-2021  08:28:50.388510 EAL: Virtual area found at 0x3280000000 (size =
0x1000)
08-30-2021  08:28:50.388520 EAL: Memseg list allocated: 0x100000kB at
socket 1
08-30-2021  08:28:50.388524 EAL: Ask a virtual area of 0x800000000 bytes
08-30-2021  08:28:50.388528 EAL: Virtual area found at 0x32c0000000 (size =
0x800000000)
08-30-2021  08:28:50.388537 EAL: Ask a virtual area of 0x1000 bytes
08-30-2021  08:28:50.388542 EAL: Virtual area found at 0x3ac0000000 (size =
0x1000)
08-30-2021  08:28:50.388552 EAL: Memseg list allocated: 0x100000kB at
socket 1
08-30-2021  08:28:50.388555 EAL: Ask a virtual area of 0x800000000 bytes
08-30-2021  08:28:50.388560 EAL: Virtual area found at 0x3b00000000 (size =
0x800000000)
08-30-2021  08:28:50.388565 EAL: Creating 16 segment lists: n_segs:1024
socket_id:0 hugepage_sz:2097152
08-30-2021  08:28:50.388569 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.388573 EAL: Virtual area found at 0x4300000000 (size =
0xd000)
08-30-2021  08:28:50.388610 EAL: Memseg list allocated: 0x800kB at socket 0
08-30-2021  08:28:50.388614 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.388619 EAL: Virtual area found at 0x4300200000 (size =
0x80000000)
08-30-2021  08:28:50.388625 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.388630 EAL: Virtual area found at 0x4380200000 (size =
0xd000)
08-30-2021  08:28:50.388666 EAL: Memseg list allocated: 0x800kB at socket 0
08-30-2021  08:28:50.388670 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.388675 EAL: Virtual area found at 0x4380400000 (size =
0x80000000)
08-30-2021  08:28:50.388680 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.388685 EAL: Virtual area found at 0x4400400000 (size =
0xd000)
08-30-2021  08:28:50.388723 EAL: Memseg list allocated: 0x800kB at socket 0
08-30-2021  08:28:50.388726 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.388734 EAL: Virtual area found at 0x4400600000 (size =
0x80000000)
08-30-2021  08:28:50.388740 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.388744 EAL: Virtual area found at 0x4480600000 (size =
0xd000)
08-30-2021  08:28:50.388782 EAL: Memseg list allocated: 0x800kB at socket 0
08-30-2021  08:28:50.388786 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.388791 EAL: Virtual area found at 0x4480800000 (size =
0x80000000)
08-30-2021  08:28:50.388796 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.388801 EAL: Virtual area found at 0x4500800000 (size =
0xd000)
08-30-2021  08:28:50.388837 EAL: Memseg list allocated: 0x800kB at socket 0
08-30-2021  08:28:50.388841 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.388845 EAL: Virtual area found at 0x4500a00000 (size =
0x80000000)
08-30-2021  08:28:50.388851 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.388856 EAL: Virtual area found at 0x4580a00000 (size =
0xd000)
08-30-2021  08:28:50.388893 EAL: Memseg list allocated: 0x800kB at socket 0
08-30-2021  08:28:50.388896 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.388901 EAL: Virtual area found at 0x4580c00000 (size =
0x80000000)
08-30-2021  08:28:50.388907 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.388912 EAL: Virtual area found at 0x4600c00000 (size =
0xd000)
08-30-2021  08:28:50.388950 EAL: Memseg list allocated: 0x800kB at socket 0
08-30-2021  08:28:50.388954 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.388958 EAL: Virtual area found at 0x4600e00000 (size =
0x80000000)
08-30-2021  08:28:50.388964 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.388969 EAL: Virtual area found at 0x4680e00000 (size =
0xd000)
08-30-2021  08:28:50.389003 EAL: Memseg list allocated: 0x800kB at socket 0
08-30-2021  08:28:50.389007 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.389012 EAL: Virtual area found at 0x4681000000 (size =
0x80000000)
08-30-2021  08:28:50.389017 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.389022 EAL: Virtual area found at 0x4701000000 (size =
0xd000)
08-30-2021  08:28:50.389059 EAL: Memseg list allocated: 0x800kB at socket 0
08-30-2021  08:28:50.389063 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.389068 EAL: Virtual area found at 0x4701200000 (size =
0x80000000)
08-30-2021  08:28:50.389074 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.389081 EAL: Virtual area found at 0x4781200000 (size =
0xd000)
08-30-2021  08:28:50.389116 EAL: Memseg list allocated: 0x800kB at socket 0
08-30-2021  08:28:50.389120 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.389124 EAL: Virtual area found at 0x4781400000 (size =
0x80000000)
08-30-2021  08:28:50.389130 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.389135 EAL: Virtual area found at 0x4801400000 (size =
0xd000)
08-30-2021  08:28:50.389181 EAL: Memseg list allocated: 0x800kB at socket 0
08-30-2021  08:28:50.389184 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.389189 EAL: Virtual area found at 0x4801600000 (size =
0x80000000)
08-30-2021  08:28:50.389194 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.389199 EAL: Virtual area found at 0x4881600000 (size =
0xd000)
08-30-2021  08:28:50.389233 EAL: Memseg list allocated: 0x800kB at socket 0
08-30-2021  08:28:50.389236 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.389240 EAL: Virtual area found at 0x4881800000 (size =
0x80000000)
08-30-2021  08:28:50.389246 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.389250 EAL: Virtual area found at 0x4901800000 (size =
0xd000)
08-30-2021  08:28:50.389285 EAL: Memseg list allocated: 0x800kB at socket 0
08-30-2021  08:28:50.389289 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.389293 EAL: Virtual area found at 0x4901a00000 (size =
0x80000000)
08-30-2021  08:28:50.389298 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.389303 EAL: Virtual area found at 0x4981a00000 (size =
0xd000)
08-30-2021  08:28:50.389339 EAL: Memseg list allocated: 0x800kB at socket 0
08-30-2021  08:28:50.389342 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.389347 EAL: Virtual area found at 0x4981c00000 (size =
0x80000000)
08-30-2021  08:28:50.389352 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.389357 EAL: Virtual area found at 0x4a01c00000 (size =
0xd000)
08-30-2021  08:28:50.389392 EAL: Memseg list allocated: 0x800kB at socket 0
08-30-2021  08:28:50.389396 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.389400 EAL: Virtual area found at 0x4a01e00000 (size =
0x80000000)
08-30-2021  08:28:50.389406 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.389410 EAL: Virtual area found at 0x4a81e00000 (size =
0xd000)
08-30-2021  08:28:50.389446 EAL: Memseg list allocated: 0x800kB at socket 0
08-30-2021  08:28:50.389450 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.389454 EAL: Virtual area found at 0x4a82000000 (size =
0x80000000)
08-30-2021  08:28:50.389459 EAL: Creating 16 segment lists: n_segs:1024
socket_id:1 hugepage_sz:2097152
08-30-2021  08:28:50.389463 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.389468 EAL: Virtual area found at 0x4b02000000 (size =
0xd000)
08-30-2021  08:28:50.389503 EAL: Memseg list allocated: 0x800kB at socket 1
08-30-2021  08:28:50.389506 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.389511 EAL: Virtual area found at 0x4b02200000 (size =
0x80000000)
08-30-2021  08:28:50.389516 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.389520 EAL: Virtual area found at 0x4b82200000 (size =
0xd000)
08-30-2021  08:28:50.389557 EAL: Memseg list allocated: 0x800kB at socket 1
08-30-2021  08:28:50.389560 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.389565 EAL: Virtual area found at 0x4b82400000 (size =
0x80000000)
08-30-2021  08:28:50.389570 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.389575 EAL: Virtual area found at 0x4c02400000 (size =
0xd000)
08-30-2021  08:28:50.389610 EAL: Memseg list allocated: 0x800kB at socket 1
08-30-2021  08:28:50.389613 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.389618 EAL: Virtual area found at 0x4c02600000 (size =
0x80000000)
08-30-2021  08:28:50.389623 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.389628 EAL: Virtual area found at 0x4c82600000 (size =
0xd000)
08-30-2021  08:28:50.389664 EAL: Memseg list allocated: 0x800kB at socket 1
08-30-2021  08:28:50.389671 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.389676 EAL: Virtual area found at 0x4c82800000 (size =
0x80000000)
08-30-2021  08:28:50.389680 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.389685 EAL: Virtual area found at 0x4d02800000 (size =
0xd000)
08-30-2021  08:28:50.389720 EAL: Memseg list allocated: 0x800kB at socket 1
08-30-2021  08:28:50.389723 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.389728 EAL: Virtual area found at 0x4d02a00000 (size =
0x80000000)
08-30-2021  08:28:50.389733 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.389738 EAL: Virtual area found at 0x4d82a00000 (size =
0xd000)
08-30-2021  08:28:50.389773 EAL: Memseg list allocated: 0x800kB at socket 1
08-30-2021  08:28:50.389776 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.389781 EAL: Virtual area found at 0x4d82c00000 (size =
0x80000000)
08-30-2021  08:28:50.389790 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.389795 EAL: Virtual area found at 0x4e02c00000 (size =
0xd000)
08-30-2021  08:28:50.389832 EAL: Memseg list allocated: 0x800kB at socket 1
08-30-2021  08:28:50.389836 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.389840 EAL: Virtual area found at 0x4e02e00000 (size =
0x80000000)
08-30-2021  08:28:50.389846 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.389850 EAL: Virtual area found at 0x4e82e00000 (size =
0xd000)
08-30-2021  08:28:50.389886 EAL: Memseg list allocated: 0x800kB at socket 1
08-30-2021  08:28:50.389889 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.389894 EAL: Virtual area found at 0x4e83000000 (size =
0x80000000)
08-30-2021  08:28:50.389899 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.389904 EAL: Virtual area found at 0x4f03000000 (size =
0xd000)
08-30-2021  08:28:50.389945 EAL: Memseg list allocated: 0x800kB at socket 1
08-30-2021  08:28:50.389948 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.389953 EAL: Virtual area found at 0x4f03200000 (size =
0x80000000)
08-30-2021  08:28:50.389958 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.389962 EAL: Virtual area found at 0x4f83200000 (size =
0xd000)
08-30-2021  08:28:50.389997 EAL: Memseg list allocated: 0x800kB at socket 1
08-30-2021  08:28:50.390001 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.390005 EAL: Virtual area found at 0x4f83400000 (size =
0x80000000)
08-30-2021  08:28:50.390010 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.390015 EAL: Virtual area found at 0x5003400000 (size =
0xd000)
08-30-2021  08:28:50.390049 EAL: Memseg list allocated: 0x800kB at socket 1
08-30-2021  08:28:50.390052 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.390057 EAL: Virtual area found at 0x5003600000 (size =
0x80000000)
08-30-2021  08:28:50.390062 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.390067 EAL: Virtual area found at 0x5083600000 (size =
0xd000)
08-30-2021  08:28:50.390104 EAL: Memseg list allocated: 0x800kB at socket 1
08-30-2021  08:28:50.390107 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.390112 EAL: Virtual area found at 0x5083800000 (size =
0x80000000)
08-30-2021  08:28:50.390117 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.390122 EAL: Virtual area found at 0x5103800000 (size =
0xd000)
08-30-2021  08:28:50.390158 EAL: Memseg list allocated: 0x800kB at socket 1
08-30-2021  08:28:50.390161 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.390166 EAL: Virtual area found at 0x5103a00000 (size =
0x80000000)
08-30-2021  08:28:50.390172 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.390176 EAL: Virtual area found at 0x5183a00000 (size =
0xd000)
08-30-2021  08:28:50.390213 EAL: Memseg list allocated: 0x800kB at socket 1
08-30-2021  08:28:50.390216 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.390221 EAL: Virtual area found at 0x5183c00000 (size =
0x80000000)
08-30-2021  08:28:50.390226 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.390233 EAL: Virtual area found at 0x5203c00000 (size =
0xd000)
08-30-2021  08:28:50.390269 EAL: Memseg list allocated: 0x800kB at socket 1
08-30-2021  08:28:50.390272 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.390276 EAL: Virtual area found at 0x5203e00000 (size =
0x80000000)
08-30-2021  08:28:50.390282 EAL: Ask a virtual area of 0xd000 bytes
08-30-2021  08:28:50.390286 EAL: Virtual area found at 0x5283e00000 (size =
0xd000)
08-30-2021  08:28:50.390323 EAL: Memseg list allocated: 0x800kB at socket 1
08-30-2021  08:28:50.390326 EAL: Ask a virtual area of 0x80000000 bytes
08-30-2021  08:28:50.390331 EAL: Virtual area found at 0x5284000000 (size =
0x80000000)
08-30-2021  08:28:50.390439 EAL: Using memfd for anonymous memory
08-30-2021  08:28:50.390564 EAL: No shared files mode enabled, IPC is
disabled
08-30-2021  08:28:50.490727 EAL: TSC frequency is ~2700000 KHz
08-30-2021  08:28:50.490916 EAL: Master lcore 0 is ready
(tid=7f0579267480;cpuset=[0])
08-30-2021  08:28:50.491256 EAL: lcore 1 is ready
(tid=7f0573ffe700;cpuset=[0])
08-30-2021  08:28:50.503828 EAL: Trying to obtain current memory policy.
08-30-2021  08:28:50.503850 EAL: Failed to get current mempolicy: Operation
not permitted. Assuming MPOL_DEFAULT.
08-30-2021  08:28:50.503861 EAL: Setting policy MPOL_PREFERRED for socket 0
08-30-2021  08:28:50.504478 EAL: alloc_seg(): get_mempolicy: Operation not
permitted
08-30-2021  08:28:50.504500 EAL: Ask a virtual area of 0x200000 bytes
08-30-2021  08:28:50.504517 EAL: Virtual area found at 0x4300200000 (size =
0x200000)
08-30-2021  08:28:50.504539 EAL: attempted to allocate 1 segments, but only
0 were allocated
08-30-2021  08:28:50.504549 EAL: Restoring previous memory policy: 0
08-30-2021  08:28:50.504585 EAL: Trying to obtain current memory policy.
08-30-2021  08:28:50.504598 EAL: Failed to get current mempolicy: Operation
not permitted. Assuming MPOL_DEFAULT.
08-30-2021  08:28:50.504609 EAL: Setting policy MPOL_PREFERRED for socket 0
08-30-2021  08:28:50.504649 EAL: alloc_seg(): mmap() failed: Cannot
allocate memory
08-30-2021  08:28:50.504661 EAL: Ask a virtual area of 0x40000000 bytes
08-30-2021  08:28:50.504674 EAL: Virtual area found at 0x140000000 (size =
0x40000000)
08-30-2021  08:28:50.504688 EAL: attempted to allocate 1 segments, but only
0 were allocated
08-30-2021  08:28:50.504699 EAL: Restoring previous memory policy: 0
08-30-2021  08:28:50.504727 EAL: Trying to obtain current memory policy.
08-30-2021  08:28:50.504740 EAL: Failed to get current mempolicy: Operation
not permitted. Assuming MPOL_DEFAULT.
08-30-2021  08:28:50.504751 EAL: Setting policy MPOL_PREFERRED for socket 1
08-30-2021  08:28:50.505005 EAL: alloc_seg(): get_mempolicy: Operation not
permitted
08-30-2021  08:28:50.505023 EAL: Ask a virtual area of 0x200000 bytes
08-30-2021  08:28:50.505039 EAL: Virtual area found at 0x4b02200000 (size =
0x200000)
08-30-2021  08:28:50.505055 EAL: attempted to allocate 1 segments, but only
0 were allocated
08-30-2021  08:28:50.505065 EAL: Restoring previous memory policy: 0
08-30-2021  08:28:50.505092 EAL: Trying to obtain current memory policy.
08-30-2021  08:28:50.505105 EAL: Failed to get current mempolicy: Operation
not permitted. Assuming MPOL_DEFAULT.
08-30-2021  08:28:50.505115 EAL: Setting policy MPOL_PREFERRED for socket 1
08-30-2021  08:28:50.505152 EAL: alloc_seg(): mmap() failed: Cannot
allocate memory
08-30-2021  08:28:50.505163 EAL: Ask a virtual area of 0x40000000 bytes
08-30-2021  08:28:50.505176 EAL: Virtual area found at 0x2240000000 (size =
0x40000000)
08-30-2021  08:28:50.505190 EAL: attempted to allocate 1 segments, but only
0 were allocated
08-30-2021  08:28:50.505200 EAL: Restoring previous memory policy: 0
08-30-2021  08:28:50.505221 EAL: error allocating rte services array
08-30-2021  08:28:50.505246 EAL: rte_service_init() failed
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted
set_mempolicy: Operation not permitted

On Mon, Aug 30, 2021 at 1:22 PM Kamaraj P <pkamaraj@gmail.com> wrote:

> Hello All,
> Some more info.
> We are using DPDK 19.11.
>
> When we bringup application with --security-opt seccomp=unconfined
> option..
> THe application bringup successfully and didnt observe any error when DPDK
> init logs.
> Will that --security-opt seccomp=unconfined option recommended for
> non-previlege mode for DPDK application ?
> Please suggest.
>
> Thanks,
> Kamaraj
>
> On Mon, Aug 30, 2021 at 1:07 PM Kamaraj P <pkamaraj@gmail.com> wrote:
>
>> Hello All,
>>
>> We are not able to run the DPDK allocation without using privilege
>> option.
>>
>> Able to see the below erors:
>>
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> EAL: FATAL: rte_service_init() failed
>> Failed to init DPDK.set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> Failed to create mbuf for pool DPDK_POOL_0 frame_len=2048 num_mbufs=13824
>> ret (Exec format error)
>>
>> BTW we are also enabling --iova-mode=va option as part DPDK init.
>>
>> Can anyone please throw some light on this ?
>>
>> Thanks,
>> Kamaraj
>>
>

Re: [dpdk-dev] Running DPDK application with non-previlege mode

[Ferruh Yigit]

On 8/30/2021 8:52 AM, Kamaraj P wrote:
> Hello All,
> Some more info.
> We are using DPDK 19.11.
> 
> When we bringup application with --security-opt seccomp=unconfined
> option..
> THe application bringup successfully and didnt observe any error when DPDK
> init logs.
> Will that --security-opt seccomp=unconfined option recommended for
> non-previlege mode for DPDK application ?
> Please suggest.
> 

+ Anatoly, he may have experience on running on non-privilege mode.


Thomas, David,

What do you think documenting how to run as non root, we had similar question
before, if memory serves me right Red Hat was looking for same thing at some point.

If we are agree, perhaps we can find a volunteer in the tech board for it.


> Thanks,
> Kamaraj
> 
> On Mon, Aug 30, 2021 at 1:07 PM Kamaraj P <pkamaraj@gmail.com> wrote:
> 
>> Hello All,
>>
>> We are not able to run the DPDK allocation without using privilege option.
>>
>> Able to see the below erors:
>>
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> EAL: FATAL: rte_service_init() failed
>> Failed to init DPDK.set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> set_mempolicy: Operation not permitted
>> Failed to create mbuf for pool DPDK_POOL_0 frame_len=2048 num_mbufs=13824
>> ret (Exec format error)
>>
>> BTW we are also enabling --iova-mode=va option as part DPDK init.
>>
>> Can anyone please throw some light on this ?
>>
>> Thanks,
>> Kamaraj
>>

Re: [dpdk-dev] Running DPDK application with non-previlege mode

[Kamaraj P]

Thanks Ferruh.
One more option which we have figured out to resolve this error by adding
SYS_NICE capability ( --cap-add=NET_ADMIN --cap-add=SYS_RESOURCE
--cap-add=SYS_NICE).
Not sure whether it will work for all the scenarios. However the above
options will ensure DPDK application can run as non-previlage mode ?
Please suggest the right approach which should work for all the DPDK
versions.

Thanks,
Kamaraj

On Mon, Aug 30, 2021 at 4:57 PM Ferruh Yigit <ferruh.yigit@intel.com> wrote:

> On 8/30/2021 8:52 AM, Kamaraj P wrote:
> > Hello All,
> > Some more info.
> > We are using DPDK 19.11.
> >
> > When we bringup application with --security-opt seccomp=unconfined
> > option..
> > THe application bringup successfully and didnt observe any error when
> DPDK
> > init logs.
> > Will that --security-opt seccomp=unconfined option recommended for
> > non-previlege mode for DPDK application ?
> > Please suggest.
> >
>
> + Anatoly, he may have experience on running on non-privilege mode.
>
>
> Thomas, David,
>
> What do you think documenting how to run as non root, we had similar
> question
> before, if memory serves me right Red Hat was looking for same thing at
> some point.
>
> If we are agree, perhaps we can find a volunteer in the tech board for it.
>
>
> > Thanks,
> > Kamaraj
> >
> > On Mon, Aug 30, 2021 at 1:07 PM Kamaraj P <pkamaraj@gmail.com> wrote:
> >
> >> Hello All,
> >>
> >> We are not able to run the DPDK allocation without using privilege
> option.
> >>
> >> Able to see the below erors:
> >>
> >> set_mempolicy: Operation not permitted
> >> set_mempolicy: Operation not permitted
> >> set_mempolicy: Operation not permitted
> >> set_mempolicy: Operation not permitted
> >> set_mempolicy: Operation not permitted
> >> set_mempolicy: Operation not permitted
> >> set_mempolicy: Operation not permitted
> >> set_mempolicy: Operation not permitted
> >> EAL: FATAL: rte_service_init() failed
> >> Failed to init DPDK.set_mempolicy: Operation not permitted
> >> set_mempolicy: Operation not permitted
> >> set_mempolicy: Operation not permitted
> >> set_mempolicy: Operation not permitted
> >> set_mempolicy: Operation not permitted
> >> set_mempolicy: Operation not permitted
> >> set_mempolicy: Operation not permitted
> >> set_mempolicy: Operation not permitted
> >> Failed to create mbuf for pool DPDK_POOL_0 frame_len=2048
> num_mbufs=13824
> >> ret (Exec format error)
> >>
> >> BTW we are also enabling --iova-mode=va option as part DPDK init.
> >>
> >> Can anyone please throw some light on this ?
> >>
> >> Thanks,
> >> Kamaraj
> >>
>
>

Re: [dpdk-dev] Running DPDK application with non-previlege mode

[Thomas Monjalon]

30/08/2021 13:26, Ferruh Yigit:
> On 8/30/2021 8:52 AM, Kamaraj P wrote:
> > Hello All,
> > Some more info.
> > We are using DPDK 19.11.
> > 
> > When we bringup application with --security-opt seccomp=unconfined
> > option..
> > THe application bringup successfully and didnt observe any error when DPDK
> > init logs.
> > Will that --security-opt seccomp=unconfined option recommended for
> > non-previlege mode for DPDK application ?
> > Please suggest.
> > 
> 
> + Anatoly, he may have experience on running on non-privilege mode.
> 
> 
> Thomas, David,
> 
> What do you think documenting how to run as non root, we had similar question
> before, if memory serves me right Red Hat was looking for same thing at some point.

I started working on such documentation, focusing on mlx5 use case.
I need more time to complete it.

> If we are agree, perhaps we can find a volunteer in the tech board for it.

I would be volunteer, and welcome any help.

Re: [dpdk-dev] Running DPDK application with non-previlege mode

[Thomas Monjalon]

30/08/2021 13:45, Kamaraj P:
> Thanks Ferruh.
> One more option which we have figured out to resolve this error by adding
> SYS_NICE capability ( --cap-add=NET_ADMIN --cap-add=SYS_RESOURCE
> --cap-add=SYS_NICE).
> Not sure whether it will work for all the scenarios. However the above
> options will ensure DPDK application can run as non-previlage mode ?
> Please suggest the right approach which should work for all the DPDK
> versions.

It depends on which device/driver you use.

Here are some infos:

`SYS_ADMIN`
Required for finding IOVA physical addresses.
Not needed if using virtual addressing (DPDK default)                                                
or if Linux is older than 4.0.

`SYS_NICE`
Enable the syscalls `get_mempolicy` and `set_mempolicy`
required for NUMA memory management.
Not needed if `RTE_EAL_NUMA_AWARE_HUGEPAGES` is disabled
(explicitly or because of missing libnuma).

`SYS_RAWIO`
Enable the syscall `iopl` required for I/O port,
used for legacy virtio mode.

`NET_ADMIN`
Required for some device configuration.

`NET_RAW`
Required for mlx5 queue allocation. Enabled by default in Docker.

`IPC_LOCK`
Required for some DMA pinning.

Re: [dpdk-dev] Running DPDK application with non-previlege mode

[David Marchand]

On Mon, Aug 30, 2021 at 1:59 PM Thomas Monjalon <thomas@monjalon.net> wrote:
>
> 30/08/2021 13:26, Ferruh Yigit:
> > On 8/30/2021 8:52 AM, Kamaraj P wrote:
> > > Hello All,
> > > Some more info.
> > > We are using DPDK 19.11.
> > >
> > > When we bringup application with --security-opt seccomp=unconfined
> > > option..
> > > THe application bringup successfully and didnt observe any error when DPDK
> > > init logs.
> > > Will that --security-opt seccomp=unconfined option recommended for
> > > non-previlege mode for DPDK application ?
> > > Please suggest.
> > >
> >
> > + Anatoly, he may have experience on running on non-privilege mode.
> >
> >
> > Thomas, David,
> >
> > What do you think documenting how to run as non root, we had similar question
> > before, if memory serves me right Red Hat was looking for same thing at some point.
>
> I started working on such documentation, focusing on mlx5 use case.
> I need more time to complete it.
>
> > If we are agree, perhaps we can find a volunteer in the tech board for it.
>
> I would be volunteer, and welcome any help.

OVS already did some integration for this, and I can help too.


-- 
David Marchand

Re: [dpdk-dev] Running DPDK application with non-previlege mode

[Kamaraj P]

Hi Thomas,
We are trying with the IGB_UIO driver in our DPDK application.
Is there any documentation where we need to start to run a DPDK application
with minimal system capability?
Also please let us know if there is any known dependency with DPDK versions
(dpdk application with 18, 19.11 versions etc) when we run with sys capabilit.


Hi David,
Can you please share with us the pointer for OVS integration(DPDK running
as non-privileged mode ?)

Thanks,
Kamaraj

On Mon, Aug 30, 2021 at 5:36 PM David Marchand <david.marchand@redhat.com>
wrote:

> On Mon, Aug 30, 2021 at 1:59 PM Thomas Monjalon <thomas@monjalon.net>
> wrote:
> >
> > 30/08/2021 13:26, Ferruh Yigit:
> > > On 8/30/2021 8:52 AM, Kamaraj P wrote:
> > > > Hello All,
> > > > Some more info.
> > > > We are using DPDK 19.11.
> > > >
> > > > When we bringup application with --security-opt seccomp=unconfined
> > > > option..
> > > > THe application bringup successfully and didnt observe any error
> when DPDK
> > > > init logs.
> > > > Will that --security-opt seccomp=unconfined option recommended for
> > > > non-previlege mode for DPDK application ?
> > > > Please suggest.
> > > >
> > >
> > > + Anatoly, he may have experience on running on non-privilege mode.
> > >
> > >
> > > Thomas, David,
> > >
> > > What do you think documenting how to run as non root, we had similar
> question
> > > before, if memory serves me right Red Hat was looking for same thing
> at some point.
> >
> > I started working on such documentation, focusing on mlx5 use case.
> > I need more time to complete it.
> >
> > > If we are agree, perhaps we can find a volunteer in the tech board for
> it.
> >
> > I would be volunteer, and welcome any help.
>
> OVS already did some integration for this, and I can help too.
>
>
> --
> David Marchand
>
>

Re: [dpdk-dev] Running DPDK application with non-previlege mode

[David Marchand]

On Tue, Aug 31, 2021 at 5:27 PM Kamaraj P <pkamaraj@gmail.com> wrote:
>
> Hi Thomas,
> We are trying with the IGB_UIO driver in our DPDK application.

Running with igb-uio as a non priviledged user is not possible (or, at
best, makes little sense).


> Is there any documentation where we need to start to run a DPDK application with minimal system capability?
> Also please let us know if there is any known dependency with DPDK versions (dpdk application with 18, 19.11 versions etc) when we run with sys capabilit.
>
> Hi David,
> Can you please share with us the pointer for OVS integration(DPDK running as non-privileged mode ?)

I don't have a full list, here is what I have in mind.

For non mellanox devices, you'll have to rely on vfio-pci bound
devices and setup access to those fds.
https://github.com/openvswitch/ovs/blob/master/rhel/usr_lib_udev_rules.d_91-vfio.rules

For mellanox devices and some parts of dpdk, you need (quite) some capabilities:
https://github.com/openvswitch/ovs/blob/master/lib/daemon-unix.c#L812

There are also hugepages accesses to consider:
https://github.com/openvswitch/ovs/blob/master/rhel/usr_lib_systemd_system_ovs-vswitchd.service.in#L20

There are selinux considerations too.


-- 
David Marchand

Re: [dpdk-dev] Running DPDK application with non-previlege mode

[Kamaraj P]

Thanks David. Will check it out.

BTW are there any steps where DPDK testpmd can run as a non privileged user
mode ( with any driver )?
Please share if you have any pointers.

Thanks,
Kamaraj

On Tue, Aug 31, 2021 at 9:05 PM David Marchand <david.marchand@redhat.com>
wrote:

> On Tue, Aug 31, 2021 at 5:27 PM Kamaraj P <pkamaraj@gmail.com> wrote:
> >
> > Hi Thomas,
> > We are trying with the IGB_UIO driver in our DPDK application.
>
> Running with igb-uio as a non priviledged user is not possible (or, at
> best, makes little sense).
>
>
> > Is there any documentation where we need to start to run a DPDK
> application with minimal system capability?
> > Also please let us know if there is any known dependency with DPDK
> versions (dpdk application with 18, 19.11 versions etc) when we run with
> sys capabilit.
> >
> > Hi David,
> > Can you please share with us the pointer for OVS integration(DPDK
> running as non-privileged mode ?)
>
> I don't have a full list, here is what I have in mind.
>
> For non mellanox devices, you'll have to rely on vfio-pci bound
> devices and setup access to those fds.
>
> https://github.com/openvswitch/ovs/blob/master/rhel/usr_lib_udev_rules.d_91-vfio.rules
>
> For mellanox devices and some parts of dpdk, you need (quite) some
> capabilities:
> https://github.com/openvswitch/ovs/blob/master/lib/daemon-unix.c#L812
>
> There are also hugepages accesses to consider:
>
> https://github.com/openvswitch/ovs/blob/master/rhel/usr_lib_systemd_system_ovs-vswitchd.service.in#L20
>
> There are selinux considerations too.
>
>
> --
> David Marchand
>
>

Re: [dpdk-dev] Running DPDK application with non-previlege mode

[Aaron Conole]

David Marchand <david.marchand@redhat.com> writes:

> On Tue, Aug 31, 2021 at 5:27 PM Kamaraj P <pkamaraj@gmail.com> wrote:
>>
>> Hi Thomas,
>> We are trying with the IGB_UIO driver in our DPDK application.
>
> Running with igb-uio as a non priviledged user is not possible (or, at
> best, makes little sense).
>
>
>> Is there any documentation where we need to start to run a DPDK
>> application with minimal system capability?
>> Also please let us know if there is any known dependency with DPDK
>> versions (dpdk application with 18, 19.11 versions etc) when we run
>> with sys capabilit.
>>
>> Hi David,
>> Can you please share with us the pointer for OVS integration(DPDK running as non-privileged mode ?)
>
> I don't have a full list, here is what I have in mind.
>
> For non mellanox devices, you'll have to rely on vfio-pci bound
> devices and setup access to those fds.
> https://github.com/openvswitch/ovs/blob/master/rhel/usr_lib_udev_rules.d_91-vfio.rules
>
> For mellanox devices and some parts of dpdk, you need (quite) some capabilities:
> https://github.com/openvswitch/ovs/blob/master/lib/daemon-unix.c#L812
>
> There are also hugepages accesses to consider:
> https://github.com/openvswitch/ovs/blob/master/rhel/usr_lib_systemd_system_ovs-vswitchd.service.in#L20
>
> There are selinux considerations too.

See: https://github.com/openvswitch/ovs/tree/master/selinux

Additionally, you might need to do some additional work for whatever LSM
you use.  For example, AppArmor, etc.

Re: [dpdk-dev] Running DPDK application with non-previlege mode

[Bruce Richardson]

On Tue, Aug 31, 2021 at 09:50:43PM +0530, Kamaraj P wrote:
> Thanks David. Will check it out.
> 
> BTW are there any steps where DPDK testpmd can run as a non privileged user
> mode ( with any driver )?
> Please share if you have any pointers.
> 
> Thanks,
> Kamaraj
> 
Not sure if this is generally applicable but I ran a test using testpmd as
a non-root user on my Ubuntu 21.04 system.

I bound a couple of ports using the i40e driver to DPDK using vfio-pci
kernel driver, and then did a chmod on the /dev/vfio/ nodes for them to
give the user access. I also gave the user rw access to the hugepage mount
point I had created. Thereafter testpmd ran fine as a non-root user and I
was able to put traffic through it.

Regards,
/Bruce

Re: [dpdk-dev] Running DPDK application with non-previlege mode

[Kamaraj P]

Thanks Bruce.

BTW we are trying to run our application as docker container.
We may need to pass the parameters(system capability) along with docker
command line to mount the hugepages ?
Like this : https://github.com/usnistgov/ndn-dpdk/blob/main/docs/Docker.md

Please share your thoughts.

Thanks,
Kamaraj

On Wed, Sep 1, 2021 at 1:14 AM Bruce Richardson <bruce.richardson@intel.com>
wrote:

> On Tue, Aug 31, 2021 at 09:50:43PM +0530, Kamaraj P wrote:
> > Thanks David. Will check it out.
> >
> > BTW are there any steps where DPDK testpmd can run as a non privileged
> user
> > mode ( with any driver )?
> > Please share if you have any pointers.
> >
> > Thanks,
> > Kamaraj
> >
> Not sure if this is generally applicable but I ran a test using testpmd as
> a non-root user on my Ubuntu 21.04 system.
>
> I bound a couple of ports using the i40e driver to DPDK using vfio-pci
> kernel driver, and then did a chmod on the /dev/vfio/ nodes for them to
> give the user access. I also gave the user rw access to the hugepage mount
> point I had created. Thereafter testpmd ran fine as a non-root user and I
> was able to put traffic through it.
>
> Regards,
> /Bruce
>

Re: [dpdk-dev] Running DPDK application with non-previlege mode

[Thomas Monjalon]

01/09/2021 18:09, Kamaraj P:
> Thanks Bruce.
> 
> BTW we are trying to run our application as docker container.
> We may need to pass the parameters(system capability) along with docker
> command line to mount the hugepages ?
> Like this : https://github.com/usnistgov/ndn-dpdk/blob/main/docs/Docker.md
> 
> Please share your thoughts.

The easiest is to run with --in-memory option.

If you really want the hugetlb files (for multi-process),
use such docker option:
--mount type=bind,src=/dev/hugepages,dst=/dev/hugepages

Re: [dpdk-dev] Running DPDK application with non-previlege mode

[Kamaraj P]

Hello Thomas,
THanks for the suggestion.
Yes. Our DPDK application already has an in-memory option.
BTW we are not using a multi-process environment for our DPDK application.

Thanks,
Kamaraj


On Wed, Sep 1, 2021 at 11:23 PM Thomas Monjalon <thomas@monjalon.net> wrote:

> 01/09/2021 18:09, Kamaraj P:
> > Thanks Bruce.
> >
> > BTW we are trying to run our application as docker container.
> > We may need to pass the parameters(system capability) along with docker
> > command line to mount the hugepages ?
> > Like this :
> https://github.com/usnistgov/ndn-dpdk/blob/main/docs/Docker.md
> >
> > Please share your thoughts.
>
> The easiest is to run with --in-memory option.
>
> If you really want the hugetlb files (for multi-process),
> use such docker option:
> --mount type=bind,src=/dev/hugepages,dst=/dev/hugepages
>
>
>
>

Re: [dpdk-dev] Running DPDK application with non-previlege mode

[Kamaraj P]

Hi Thomas/Antoly,

We have tried with the below capability to start a DPDK application as a
container.
--cap-add=NET_ADMIN --cap-add=SYS_RESOURCE  --cap-add=SYS_NICE

Still We could see the failures when rte_eali_init() ..

09-06-2021  10:48:37.423583 EAL: NUMA is not supported.
*09-06-2021  10:48:37.423895 EAL: alloc_seg(): get_mempolicy: Function not
implemented  ==> Does this sound like virtual memory is not enough in the
running system (because of NUMA not supported )?*
09-06-2021  10:48:37.423910 EAL: Ask a virtual area of 0x200000 bytes
09-06-2021  10:48:37.423919 EAL: Virtual area found at 0x2200200000 (size =
0x200000)
09-06-2021  10:48:37.423933 EAL: attempted to allocate 1 segments, but only
0 were allocated
09-06-2021  10:48:37.423945 EAL: NUMA is not supported.
*09-06-2021  10:48:37.427811 EAL: alloc_seg(): mmap() failed: Cannot
allocate memory ==>  SYS_RESOURCE would suffice here ?*
09-06-2021  10:48:37.427821 EAL: Ask a virtual area of 0x40000000 bytes
09-06-2021  10:48:37.427829 EAL: Virtual area found at 0x140000000 (size =
0x40000000)
09-06-2021  10:48:37.427839 EAL: attempted to allocate 1 segments, but only
0 were allocated
09-06-2021  10:48:37.427847 EAL: error allocating rte services array
09-06-2021  10:48:37.427869 EAL: rte_service_init() failed


As for the dpdk options when bringing up our application,
--log-level=*:8
--lcores=(0-1)@0
--in-memory
-d/usr/lib64/dpdk-19/librte_pmd_ixgbe.so.20.0
-d/usr/lib64/dpdk-19/librte_pmd_e1000.so.20.0
-d/usr/lib64/dpdk-19/librte_pmd_bnxt.so.20.0
--vdev=net_af_packet0,iface=dpbr_100
--vdev=net_af_packet1,iface=asac-in
--vdev=net_af_packet2,iface=asac-out
*--iova-mode=va  ==> will valid here ?*

Would assume some of the flags were not enough to run DPDK on top of our
environment ? Any memory configuration which needs to be checked for the
underlying system ?
Please share your thoughts.

Thanks,
Kamaraj

On Sun, Sep 5, 2021 at 10:24 PM Kamaraj P <pkamaraj@gmail.com> wrote:

> Hello Thomas,
> THanks for the suggestion.
> Yes. Our DPDK application already has an in-memory option.
> BTW we are not using a multi-process environment for our DPDK application.
>
> Thanks,
> Kamaraj
>
>
> On Wed, Sep 1, 2021 at 11:23 PM Thomas Monjalon <thomas@monjalon.net>
> wrote:
>
>> 01/09/2021 18:09, Kamaraj P:
>> > Thanks Bruce.
>> >
>> > BTW we are trying to run our application as docker container.
>> > We may need to pass the parameters(system capability) along with docker
>> > command line to mount the hugepages ?
>> > Like this :
>> https://github.com/usnistgov/ndn-dpdk/blob/main/docs/Docker.md
>> >
>> > Please share your thoughts.
>>
>> The easiest is to run with --in-memory option.
>>
>> If you really want the hugetlb files (for multi-process),
>> use such docker option:
>> --mount type=bind,src=/dev/hugepages,dst=/dev/hugepages
>>
>>
>>
>>