DPDK CI discussions
 help / color / mirror / Atom feed
From: Patrick Robb <probb@iol.unh.edu>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: "Ruifeng Wang" <Ruifeng.Wang@arm.com>,
	"Juraj Linkeš" <juraj.linkes@pantheon.tech>,
	"Dharmik Jayesh Thakkar" <DharmikJayesh.Thakkar@arm.com>,
	"David Marchand" <david.marchand@redhat.com>,
	"ci@dpdk.org" <ci@dpdk.org>, nd <nd@arm.com>,
	"Wathsala Wathawana Vithanage" <wathsala.vithanage@arm.com>,
	"Paul Szczepanek" <Paul.Szczepanek@arm.com>
Subject: Re: Intel QAT 8970 accel card on ARM Ampere Server
Date: Wed, 28 Feb 2024 15:00:04 -0500	[thread overview]
Message-ID: <CAJvnSUDmdUSBbUdK2Wc9Ag7wyn-ffggwy6wXpfa_DSo+Z-htZg@mail.gmail.com> (raw)
In-Reply-To: <EFC730AB-51DB-404E-96A9-D7736E67FDA3@arm.com>

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

quick update:

I could bind the QAT VFs to vfio-pci after using the module loading options
Dharmik mentioned.

First I tested SYM QAT pmd from dpdk test on the VF and got:

 + Tests Total :       751
 + Tests Skipped :     257
 + Tests Executed :    659
 + Tests Unsupported:   0
 + Tests Passed :      494
 + Tests Failed :       0
 + ------------------------------------------------------- +
Test OK

I can try the crypto performance DTS testsuite next. Let me know if you
have any thoughts.



On Tue, Feb 27, 2024 at 8:51 AM Honnappa Nagarahalli <
Honnappa.Nagarahalli@arm.com> wrote:

> + Paul, Wathsala
>
> > On Feb 27, 2024, at 12:58 AM, Patrick Robb <probb@iol.unh.edu> wrote:
> >
> >
> >
> > On Tue, Nov 14, 2023 at 2:35 AM Ruifeng Wang <Ruifeng.Wang@arm.com>
> wrote:
> > Hi Patrick,
> >  It seems kernel v5.15 has a defect on this. A similar issue was fixed
> by commit:
> > 40da865381ad ("crypto: qat - remove unneeded packed attribute")
> >  Could you patch the kernel and try again?
> >
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=40da865381ad061ab75a7a9da469ed4e623bdfeb
> >  Thanks,
> > Ruifeng
> >
> > Hi Ruifeng,
> >
> > Sorry for the delay on this - there has been a work item backlog at the
> Community Lab we've been working through.
> >
> > I did rebuild the patch today with these changes from the commit (or
> similar, as the commit above was for the qat_common file in a different
> state, but I tried to remain as true to the commit as possible).
> >
> > And that does seem to have resolved the seg fault problem! Thank you so
> much for picking this commit out of obscurity and sending it our way!
> >
> > root@arm-ampere-dut:~# echo 16 >
> /sys/bus/pci/drivers/c6xx/0000:03:00.0/sriov_numvfs
> > root@arm-ampere-dut:~# cat
> /sys/bus/pci/drivers/c6xx/0000:03:00.0/sriov_numvfs
> > 16
> >
> > Wunderbar!
> >
> > The only other thing I changed (just because I was floating the idea
> with Dharmik before) was in the kernel .config I changed the qat_c62x and
> qat_c62xvf modules from statically built in (=y) to loadable (=m). Of
> course, this should not matter, and I presume the change in behavior
> relates to those brought in from the commit above. I just want to present
> fully all changes made so there is a complete picture.
> >
> > I will continue on this tomorrow according to where this conversation
> left off, and try to move this quickly. If indeed there are no more
> blockers I think we are very close. As a reminder, when standing up a new
> testing plan, we want to make sure at least 1 rep from each vendor has SSH
> access and can remotely login to help with system tuning, troubleshooting,
> etc. for the testbed and test plan. Who would be the best person from ARM
> for this at this time, given the context on QAT testing? Ruifeng? Dharmik?
> Someone else?
> >
> > Thanks, I'll keep yall apprised of the situation.
> >
>
>

[-- Attachment #2: Type: text/html, Size: 3917 bytes --]

  reply	other threads:[~2024-02-28 20:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-31 17:13 Patrick Robb
2023-08-04  9:48 ` Ruifeng Wang
2023-08-08  7:07   ` Juraj Linkeš
2023-08-08  7:11     ` Ruifeng Wang
2023-08-11 21:18       ` Patrick Robb
2023-08-21  8:45         ` Juraj Linkeš
2023-08-30  0:05           ` Patrick Robb
2023-09-01 21:30           ` Patrick Robb
2023-09-11  8:13             ` Juraj Linkeš
2023-09-20 18:28               ` Patrick Robb
2023-09-25 15:19                 ` Ruifeng Wang
2023-10-09 16:34                   ` Patrick Robb
2023-10-10  2:28                     ` Patrick Robb
2023-10-10  3:55                       ` Dharmik Jayesh Thakkar
2023-10-10  7:25                         ` David Marchand
2023-10-10 15:03                           ` Dharmik Jayesh Thakkar
2023-10-10 15:12                             ` David Marchand
2023-10-10 15:59                         ` Patrick Robb
2023-10-10 21:50                           ` Dharmik Jayesh Thakkar
2023-10-11  8:14                           ` Juraj Linkeš
2023-10-11 20:13                             ` Patrick Robb
2023-11-02 22:00                               ` Patrick Robb
2023-11-14  7:34                                 ` Ruifeng Wang
2023-11-14 14:36                                   ` Patrick Robb
2024-02-27  6:58                                   ` Patrick Robb
2024-02-27 13:50                                     ` Honnappa Nagarahalli
2024-02-28 20:00                                       ` Patrick Robb [this message]
2024-02-28 20:40                                         ` Honnappa Nagarahalli
2024-03-07  5:27                                           ` Patrick Robb
2024-03-07  7:56                                             ` David Marchand
2023-10-11 11:51                           ` David Marchand

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=CAJvnSUDmdUSBbUdK2Wc9Ag7wyn-ffggwy6wXpfa_DSo+Z-htZg@mail.gmail.com \
    --to=probb@iol.unh.edu \
    --cc=DharmikJayesh.Thakkar@arm.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=Paul.Szczepanek@arm.com \
    --cc=Ruifeng.Wang@arm.com \
    --cc=ci@dpdk.org \
    --cc=david.marchand@redhat.com \
    --cc=juraj.linkes@pantheon.tech \
    --cc=nd@arm.com \
    --cc=wathsala.vithanage@arm.com \
    /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).