From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 218C243BCF; Fri, 1 Mar 2024 14:56:26 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E8E9F433F2; Fri, 1 Mar 2024 14:56:25 +0100 (CET) Received: from inbox.dpdk.org (inbox.dpdk.org [95.142.172.178]) by mails.dpdk.org (Postfix) with ESMTP id D7F33433F2 for ; Fri, 1 Mar 2024 14:56:23 +0100 (CET) Received: by inbox.dpdk.org (Postfix, from userid 33) id D2EAA43BD7; Fri, 1 Mar 2024 14:56:23 +0100 (CET) From: bugzilla@dpdk.org To: dev@dpdk.org Subject: [DPDK/examples Bug 1393] examples/l3fwd: in eventmode RX queue setup doesn't obey numa Date: Fri, 01 Mar 2024 13:56:23 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: examples X-Bugzilla-Version: 23.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: konstantin.v.ananyev@yandex.ru X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: multipart/alternative; boundary=17093013831.3C0Ef0b71.668093 Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org --17093013831.3C0Ef0b71.668093 Date: Fri, 1 Mar 2024 14:56:23 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All https://bugs.dpdk.org/show_bug.cgi?id=3D1393 Bug ID: 1393 Summary: examples/l3fwd: in eventmode RX queue setup doesn't obey numa Product: DPDK Version: 23.11 Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: Normal Component: examples Assignee: dev@dpdk.org Reporter: konstantin.v.ananyev@yandex.ru Target Milestone: --- Reproducible with latest DPDK main branch (24.03.rc1) Starting l3fwd in event mode with all cores/NICs on numa-socket #1 will fai= l: dpdk-l3fwd --lcores=3D49,51,53,57 -n 6 \ -a ca:00.0 -a ca:00.1 -a cb:00.0 -a cb:00.1 -s 0x8000000000000 --vdev event= _sw0 -- \ -L -P -p f --rx-queue-size 1024 --tx-queue-size 1024 --mode eventdev \ --eventq-sched=3Dordered --rule_ipv4=3Dtest/l3fwd_lpm_v4_u1.cfg \ --rule_ipv6=3Dtest/l3fwd_lpm_v6_u1.cfg .... ... ETHDEV: Ambiguous Rx mempools configuration EAL: Error - exiting with code: 1 Cause: rte_eth_rx_queue_setup: err=3D-22, port=3D0, eth_qid: 0 Reason for that: all lcores I specified are from numa-socket #1, so there is no mempool for numa-socket #0, while in event mode l3fwd_eth_dev_port_setup() *always* tri= es to use mempool for numa-socket 0. examples/l3fwd/l3fwd_event.c: static void l3fwd_eth_dev_port_setup(struct rte_eth_conf *port_conf) { ... for (eth_qid =3D 0; eth_qid < evt_rsrc->eth_rx_queues; eth_qid++) { if (!evt_rsrc->per_port_pool) ret =3D rte_eth_rx_queue_setup(port_id, eth= _qid, nb_rxd, 0, &rxconf, evt_rsrc->pkt_pool[0][0]); else ret =3D rte_eth_rx_queue_setup(port_id, eth= _qid, nb_rxd, 0, &rxconf, evt_rsrc->pkt_pool[port_id][0]); For proper numa support, I expect it to be something like: int socket_id =3D l3fwd_event_deduce_rx_service_socket_id(...); ret =3D rte_eth_rx_queue_setup(..., evt_rsrc->pkt_pool[port_id][socket_id]); To overcome the problem, use '--no-numa' l3fwd cmd-line flag. --=20 You are receiving this mail because: You are the assignee for the bug.= --17093013831.3C0Ef0b71.668093 Date: Fri, 1 Mar 2024 14:56:23 +0100 MIME-Version: 1.0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All
Bug ID
Product DPDK
Version 23.11
Hardware All
OS All
Status UNCONFIRMED
Severity normal
Priority Normal
Component examples
Assignee dev@dpdk.org
Reporter konstantin.v.ananyev@yandex.ru
Target Milestone --- 

Reproducible with latest DPDK main=
 branch (24.03.rc1)

Starting l3fwd in event mode with all cores/NICs on numa-socket #1 will fai=
l:

dpdk-l3fwd --lcores=3D49,51,53,57 -n 6 \
-a ca:00.0 -a ca:00.1 -a cb:00.0 -a cb:00.1 -s 0x8000000000000 --vdev event=
_sw0
-- \
-L -P -p f --rx-queue-size 1024 --tx-queue-size 1024 --mode eventdev \
--eventq-sched=3Dordered --rule_ipv4=3Dtest/l3fwd_lpm_v4_u1.cfg \
--rule_ipv6=3Dtest/l3fwd_lpm_v6_u1.cfg
....
...
ETHDEV: Ambiguous Rx mempools configuration
EAL: Error - exiting with code: 1
  Cause: rte_eth_rx_queue_setup: err=3D-22, port=3D0, eth_qid: 0

Reason for that:
all lcores I specified are from numa-socket #1, so there is no mempool for
numa-socket #0, while in event mode l3fwd_eth_dev_port_setup() *always* tri=
es
to use mempool for numa-socket 0.
examples/l3fwd/l3fwd_event.c:
static void
l3fwd_eth_dev_port_setup(struct rte_eth_conf *port_conf)
{
   ...
   for (eth_qid =3D 0; eth_qid < evt_rsrc->eth_rx_queues;
                     eth_qid++) {
                        if (!evt_rsrc->per_port_pool)
                                ret =3D rte_eth_rx_queue_setup(port_id, eth=
_qid,
                                        nb_rxd, 0, &rxconf,
                                        evt_rsrc->pkt_pool[0][0]);
                        else
                                ret =3D rte_eth_rx_queue_setup(port_id, eth=
_qid,
                                        nb_rxd, 0, &rxconf,
                                        evt_rsrc->pkt_pool[port_id][0]);

For proper numa support, I expect it to be something like:

int socket_id =3D l3fwd_event_deduce_rx_service_socket_id(...);
ret =3D rte_eth_rx_queue_setup(..., evt_rsrc->pkt_pool[port_id][socket_i=
d]);

To overcome the problem, use '--no-numa' l3fwd cmd-line flag.

You are receiving this mail because:
  • You are the assignee for the bug.
=20=20=20=20=20=20=20=20=20=20
= --17093013831.3C0Ef0b71.668093--