DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Patrick Robb <probb@iol.unh.edu>
Cc: dev@dpdk.org
Subject: Re: [PATCH 0/7] bnxt bug fixes
Date: Wed, 21 Feb 2024 19:20:46 -0800	[thread overview]
Message-ID: <CACZ4nhtOVtE3BgT=kAcaU4R262N=GuAq-=Z9nz1cw+R60tG4zg@mail.gmail.com> (raw)
In-Reply-To: <CAJvnSUCqE4AMCv7q+2i_B1TK4XXZ+7CtnA-eBHYJahUjZjz76A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3713 bytes --]

On Wed, Feb 21, 2024 at 6:50 PM Patrick Robb <probb@iol.unh.edu> wrote:
>
> https://patchwork.dpdk.org/project/dpdk/patch/20240208171330.31139-8-ajit.khaparde@broadcom.com/
>
> Hi Ajit,
>
> So you know, this series did fail in CI testing, and now that it is merged to main, all patchseries are failing DTS at EAL. Performance testing is also offline for the same reason.
>
> I will run the niccli utility to upgrade broadcom NIC firmware on the system and give it a rerun. Otherwise, let me know what you think.
>
> This occurs on our ARM Ampere server, with the BCM57414 NetXtreme-E 10Gb/25Gb
>
> 21:02:08   [00;36m                   TestScatter: Test Case test_scatter_mbuf_2048 Begin [0m
> 21:02:08  dut.arm-ampere-dut.dpdklab.iol.unh.edu: x86_64-native-linux-gcc/app/dpdk-testpmd -l 1,2 -n 4 -a 0007:01:00.0 -a 0007:01:00.1 --file-prefix=dpdk_2978774_20240222015854   -- -i --mbcache=200 --mbuf-size=1024 --portmask=0x1 --max-pkt-len=9000 --port-topology=loop --tx-offloads=0x00008000 [0m
> 21:04:14   [01;31m                   TestScatter: Test Case test_scatter_mbuf_2048 Result FAILED: TIMEOUT on x86_64-native-linux-gcc/app/dpdk-testpmd -l 1,2 -n 4 -a 0007:01:00.0 -a 0007:01:00.1 --file-prefix=dpdk_2978774_20240222015854   -- -i --mbcache=200 --mbuf-size=1024 --portmask=0x1 --max-pkt-len=9000 --port-topology=loop --tx-offloads=0x00008000 [0m
> 21:04:14   [01;31m                   TestScatter: EAL: Detected CPU lcores: 160
> 21:04:14  EAL: Detected NUMA nodes: 2
> 21:04:14  EAL: Detected static linkage of DPDK
> 21:04:14  EAL: Multi-process socket /var/run/dpdk/dpdk_2978774_20240222015854/mp_socket
> 21:04:14  EAL: Selected IOVA mode 'VA'
> 21:04:14  EAL: VFIO support initialized
> 21:04:14  EAL: Using IOMMU type 1 (Type 1)
> 21:04:14  EAL: Probe PCI driver: net_bnxt (14e4:16d7) device: 0007:01:00.0 (socket 1)
> 21:04:14  Segmentation fault (core dumped)
>
> I'll let you know how reruns go.

Ok Thanks for bringing it to my attention. Let me know how the rerun goes.
I had run the tests on my ARM setup and did not see the problem.
Let me try again.

Thanks
Ajit



>
> On Thu, Feb 8, 2024 at 4:51 PM Ajit Khaparde <ajit.khaparde@broadcom.com> wrote:
>>
>> On Thu, Feb 8, 2024 at 9:13 AM Ajit Khaparde <ajit.khaparde@broadcom.com> wrote:
>> >
>> > Patchset with bug fixes for bnxt PMD.
>> > Patch based against the
>> > next-net-brcm for-next-net branch.
>> >
>> > Please apply.
>> Patchset merged to the dpdk-next-brcm for-next-net branch.
>> Thanks
>>
>> >
>> > Ajit Khaparde (4):
>> >   net/bnxt: modify locking for representor Tx
>> >   net/bnxt: refactor VNIC context cleanup
>> >   net/bnxt: update consumer index of NQ regularly
>> >   net/bnxt: update RSS algorithm capability
>> >
>> > Damodharam Ammepalli (1):
>> >   net/bnxt: cleanup vnic ref count
>> >
>> > Kishore Padmanabha (1):
>> >   net/bnxt: avoid seg fault in Tx queue release
>> >
>> > Shuanglin Wang (1):
>> >   net/bnxt: adjust session name on multi host system
>> >
>> >  drivers/net/bnxt/bnxt.h            |  2 +-
>> >  drivers/net/bnxt/bnxt_ethdev.c     | 14 +++-----
>> >  drivers/net/bnxt/bnxt_hwrm.c       | 16 +++++++--
>> >  drivers/net/bnxt/bnxt_irq.c        | 26 +++++++++++---
>> >  drivers/net/bnxt/bnxt_reps.c       |  6 ++--
>> >  drivers/net/bnxt/bnxt_txq.c        |  8 ++++-
>> >  drivers/net/bnxt/bnxt_txq.h        |  1 +
>> >  drivers/net/bnxt/bnxt_txr.c        | 13 +++++++
>> >  drivers/net/bnxt/bnxt_txr.h        |  4 ++-
>> >  drivers/net/bnxt/tf_ulp/bnxt_ulp.c | 58 ++++++++++++++++++++++++++++++
>> >  10 files changed, 125 insertions(+), 23 deletions(-)
>> >
>> > --
>> > 2.39.2 (Apple Git-143)
>> >
>
>

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4218 bytes --]

      reply	other threads:[~2024-02-22  3:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-08 17:13 Ajit Khaparde
2024-02-08 17:13 ` [PATCH 1/7] net/bnxt: avoid seg fault in Tx queue release Ajit Khaparde
2024-02-08 17:13 ` [PATCH 2/7] net/bnxt: modify locking for representor Tx Ajit Khaparde
2024-02-08 17:13 ` [PATCH 3/7] net/bnxt: refactor VNIC context cleanup Ajit Khaparde
2024-02-08 17:13 ` [PATCH 4/7] net/bnxt: cleanup vnic ref count Ajit Khaparde
2024-02-08 17:13 ` [PATCH 5/7] net/bnxt: adjust session name on multi host system Ajit Khaparde
2024-02-08 17:13 ` [PATCH 6/7] net/bnxt: update consumer index of NQ regularly Ajit Khaparde
2024-02-08 17:13 ` [PATCH 7/7] net/bnxt: update RSS algorithm capability Ajit Khaparde
2024-02-08 21:50 ` [PATCH 0/7] bnxt bug fixes Ajit Khaparde
2024-02-22  2:50   ` Patrick Robb
2024-02-22  3:20     ` Ajit Khaparde [this message]

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='CACZ4nhtOVtE3BgT=kAcaU4R262N=GuAq-=Z9nz1cw+R60tG4zg@mail.gmail.com' \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=probb@iol.unh.edu \
    /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).