From: Rajasekhar Pulluru <pullururajasekhar@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: ixgbe rxq interrupt not working
Date: Wed, 8 Mar 2023 22:53:05 +0530 [thread overview]
Message-ID: <CAGA5_H4Rbk66XuYfTyVz8cFgEcyHRTHmsWLmVFHroRJr8x2BUw@mail.gmail.com> (raw)
In-Reply-To: <20230307131105.67780bcc@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 2112 bytes --]
Hi Stephen,
Downloaded https://fast.dpdk.org/rel/dpdk-22.11.1.tar.xz, built and linked
with the application. Still don't get rxq interrupt of ixgbe ports.
EAL: Detected CPU lcores: 4
EAL: Detected NUMA nodes: 1
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: VFIO support initialized
EAL: Using IOMMU type 8 (No-IOMMU)
EAL: Probe PCI driver: net_ixgbe (8086:15e4) device: 0000:02:00.0 (socket
-1)
EAL: Probe PCI driver: net_ixgbe (8086:15e4) device: 0000:02:00.1 (socket
-1)
EAL: Ignore mapping IO port bar(2)
EAL: Probe PCI driver: net_e1000_igb (8086:1521) device: 0000:04:00.1
(socket -11)
# cat /proc/interrupts | grep vfio
59: 0 0 6 0 IR-PCI-MSI 1048576-edge
vfio-msix[0](0000:02:00.0)
60: 0 6 0 0 IR-PCI-MSI 1050624-edge
vfio-msix[0](0000:02:00.1)
61: 0 0 1 0 IR-PCI-MSI 2099200-edge
vfio-msix[0](0000:04:00.1)
#>>>>> the above 3 irq's are link state change interrupt, verified by
plugging-out and plugging-in eth cable and verified the above irq counter
increments every time.
62: 0 0 0 0 IR-PCI-MSI 1050625-edge
vfio-msix[1](0000:02:00.1)
63: 0 18200 0 0 IR-PCI-MSI 2099201-edge
vfio-msix[1](0000:04:00.1)
64: 0 0 0 0 IR-PCI-MSI 1048577-edge
vfio-msix[1](0000:02:00.0)
#>>>>> igb port irq counter is non-zero (likely to be rxq), where-as the
same for ixgbe is 0.
Thanks & Regards,
Rajasekhar
On Wed, Mar 8, 2023 at 3:12 AM Stephen Hemminger <stephen@networkplumber.org>
wrote:
> On Wed, 8 Mar 2023 00:22:10 +0530
> Rajasekhar Pulluru <pullururajasekhar@gmail.com> wrote:
>
> > Hi Team,
> >
> > Bringing-up dpdk-22.07 on an intel machine with 8 ports, 4 of them driven
> > by igb and the rest of the 4 ports driven by ixgbe.
>
>
> FYI - 22.07 is not a supported release, only LTS releases like 22.11 are
> supported.
>
[-- Attachment #2: Type: text/html, Size: 2894 bytes --]
next prev parent reply other threads:[~2023-03-08 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 18:52 Rajasekhar Pulluru
2023-03-07 21:11 ` Stephen Hemminger
2023-03-08 17:23 ` Rajasekhar Pulluru [this message]
2023-03-08 0:19 ` Honnappa Nagarahalli
2023-03-08 17:24 ` Rajasekhar Pulluru
2023-03-08 17:44 ` Stephen Hemminger
2023-03-09 7:43 ` Rajasekhar Pulluru
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGA5_H4Rbk66XuYfTyVz8cFgEcyHRTHmsWLmVFHroRJr8x2BUw@mail.gmail.com \
--to=pullururajasekhar@gmail.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).