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 41F6B41E35; Wed, 8 Mar 2023 18:44:09 +0100 (CET) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E4018410EE; Wed, 8 Mar 2023 18:44:08 +0100 (CET) Received: from mail-pj1-f43.google.com (mail-pj1-f43.google.com [209.85.216.43]) by mails.dpdk.org (Postfix) with ESMTP id 59F0F40FDF for ; Wed, 8 Mar 2023 18:44:07 +0100 (CET) Received: by mail-pj1-f43.google.com with SMTP id x20-20020a17090a8a9400b00233ba727724so3955065pjn.1 for ; Wed, 08 Mar 2023 09:44:07 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=networkplumber-org.20210112.gappssmtp.com; s=20210112; t=1678297446; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:from:to:cc:subject:date :message-id:reply-to; bh=x0UwYNC4lYGLWLWuXFo8GVm1Hhn9fLGv9s+BJbd4t78=; b=V12v8yXX4tk5MUYbDmLjhoUxuw+FgsnAd1atL8EPSq0CrZI665xJp1xZ6XCFbmBTkZ QX4LQJCtScrHa31EezPzb1UCk6RaVMRfMdQQ4cm6kzcQt+eyuvJlCFXSkysy83sM+ZCr WmjypPMsL1FWA7nY/BRsdNoJyirKswAM+B1hRHJJIskloG/Vy3Kzzmv07JZ7r8I67MzR YFbDdJOkL9KJcevm9BQgTSJVO8wzM5TjErjyHY5nD9zMC4S/0U38uRdcCc/8FxDtH50R e4LYrBKLlk0We/gpRowo2NAWn+U2HcUuvFJQ8mqLymvaAcAcM7EDfIH7iaW60NaYqpuH 3iig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678297446; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=x0UwYNC4lYGLWLWuXFo8GVm1Hhn9fLGv9s+BJbd4t78=; b=4MEalRQyq0j3X7wKhCINOwlqec6adGEix/vKWbT9NgYm7lM64RZfiE9gbYDF3tR6wk KTEksPKl+YF1w9VKkjw9vQVWQVG+1JDGy+nV105yK3P6QLJ7yOZ217Pw4nCYRuQHGMvN py8dMM6kLsxGKvPkUxdtDGY7F5Jd3cZ+as0ubi86QPzH3TNPeGpaJpz1lS/J0nkjN4nX KDHmf4xBw/P02U/Utqqp+qZyiJWWgA5xSptJ0sCJsqV3H5R+gdfEdigv+ECoMQVTy48b lu8QrpE81K6nwjSXUAt+yUBXJmPirjh4rKalBP9PsIgb8k3lIEVmdaEsTBzUYLHbhlqI nv4w== X-Gm-Message-State: AO0yUKVuujmZkdFZRg1ctafMcbVxYshTLZA58b7Ka/3JLUT63FvQsqi6 taAF7l0u6S0E08IW7F8P6xut64O9oCrTVWc/WAuZ1A== X-Google-Smtp-Source: AK7set+us+km92ATvxsJxJ48TR+VDRXik6769oaRhYF0qPxs3U7GlHj67AFmccK6itv+sioPYyEdsw== X-Received: by 2002:a05:6a20:3d0c:b0:cb:6e5d:6ce0 with SMTP id y12-20020a056a203d0c00b000cb6e5d6ce0mr22027382pzi.37.1678297446302; Wed, 08 Mar 2023 09:44:06 -0800 (PST) Received: from hermes.local (204-195-120-218.wavecable.com. [204.195.120.218]) by smtp.gmail.com with ESMTPSA id p9-20020a63fe09000000b00502ea3898a7sm9548057pgh.31.2023.03.08.09.44.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 08 Mar 2023 09:44:06 -0800 (PST) Date: Wed, 8 Mar 2023 09:44:04 -0800 From: Stephen Hemminger To: Rajasekhar Pulluru Cc: Honnappa Nagarahalli , "dev@dpdk.org" , nd Subject: Re: ixgbe rxq interrupt not working Message-ID: <20230308094404.33ed0adf@hermes.local> In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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 On Wed, 8 Mar 2023 22:54:12 +0530 Rajasekhar Pulluru wrote: > No Honnappa. >=20 > Thanks & Regards, > Rajasekhar >=20 > On Wed, Mar 8, 2023 at 5:49=E2=80=AFAM Honnappa Nagarahalli < > Honnappa.Nagarahalli@arm.com> wrote: =20 >=20 > > > > > > From: Rajasekhar Pulluru > > Sent: Tuesday, March 7, 2023 12:52 PM > > To: dev@dpdk.org > > Subject: ixgbe rxq interrupt not working > > > > Hi Team, > > > > Bringing-up dpdk-22.07 on an intel machine with 8 ports, 4 of them driv= en > > by igb and the rest of the 4 ports driven by ixgbe. > > [Honnappa] Do you have packets crossing between the 2 drivers? > > > > > > I am following the below sequence to initialize these ports: > > > > dev_conf.intr_conf.lsc =3D 1; //Enable link state change interrupt > > dev_conf.intr_conf.rxq =3D 1; //Enable RX Queue Interrupt > > dev_conf.rxmode.mq_mode =3D RTE_ETH_MQ_RX_NONE; > > dev_conf.rxmode.offloads =3D 0; > > dev_conf.txmode.mq_mode =3D RTE_ETH_MQ_TX_NONE; > > dev_conf.txmode.offloads =3D 0; > > > > rte_eth_dev_configure > > rte_eth_rx_queue_setup > > rte_eth_tx_queue_setup > > rte_eth_dev_start > > data =3D port_id << CHAR_BIT | queue_id; > > rte_eth_dev_rx_intr_ctl_q(port_id, queue_id, RTE_EPOLL_PER_THREAD, > > RTE_INTR_EVENT_ADD, (void *)((uintptr_t)data)); > > rte_eth_dev_rx_intr_enable(port_id, queue_id); > > > > And then main loop repeats the below: > > > > rte_epoll_wait(RTE_EPOLL_PER_THREAD, event, 1, timeout /* 200micro-sec > > */); /* ignore return value */ > > rte_eth_dev_rx_intr_disable(port_id, queue_id); > > rte_eth_rx_burst(port_id, queue_id, pkts, num_pkts); > > rte_eth_dev_rx_intr_enable(port_id, queue_id); > > > > The code is same for all the ports, igb ports are able to come-up and rx > > packets, where-as the ixgbe ports are not able to rx packets at all. > > cat /proc/interrupts dumps vfio-msix counters for ixgbe as 0, where-as > > it's non-zero for igb. > > If I don't use/enable rxq interrupt for ixgbe (and remove epoll wait, > > interrupt enable/disable from while loop) and simply poll for > > rte_eth_rx_burst in a loop, ixgbe ports are able to rx packets. > > > > What could be wrong here? Appreciate any help. > > > > I would also like to know if there's an asynchronous rxq interrupt > > notification to the application instead of rte_epoll_wait (and sleep). > > > > Thanks & Regards, > > Rajasekhar > > =20 Does the device work as expected when not used with DPDK? I.e does the kernel driver handle it correctly. Also check the kernel dmesg log, for any relevant info. There maybe VFIO or other overlap involved.