From: "Juraj Linkeš" <juraj.linkes@pantheon.tech>
To: Patrick Robb <probb@iol.unh.edu>
Cc: Ruifeng Wang <Ruifeng.Wang@arm.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
"ci@dpdk.org" <ci@dpdk.org>, nd <nd@arm.com>
Subject: Re: Intel QAT 8970 accel card on ARM Ampere Server
Date: Mon, 11 Sep 2023 10:13:40 +0200 [thread overview]
Message-ID: <CAOb5WZZqHs3nZiVn5TY1iVk5Ao6mw=kmvBgUFwBw85U64F2V1g@mail.gmail.com> (raw)
In-Reply-To: <CAJvnSUC06FuPoubSe7=vzs2_hg_LZ=f7Di=g7nV4qqBSKis-tw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
Hi Patrick,
This is good news. How does the server fare after the restart?
Juraj
On Fri, Sep 1, 2023 at 11:30 PM Patrick Robb <probb@iol.unh.edu> wrote:
> Thanks Juraj,
>
> I did bring the system to 22.04 based on our conversation from yesterday.
> From there and from checking out to the new current kernel
> (5.15.0-82-generic) yes the diffs cleanly apply, removing the x86
> dependency on the QAT kernel drivers, and then you can make the kernel,
> enabling the QAT driver. It looks like that all worked fine.
>
> I didn't actually install and reboot with the custom kernel today because
> I don't want to do that with a production server right before the weekend,
> particularly with USA having a holiday on Monday. I will reboot with the
> custom kernel on Tuesday morning though, and then hopefully the
> compress/crypto testsuites on QAT will be unblocked. Thanks, the guidance
> is greatly appreciated.
>
> Best,
> Patrick
>
>
[-- Attachment #2: Type: text/html, Size: 1374 bytes --]
next prev parent reply other threads:[~2023-09-11 8:13 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š [this message]
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
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='CAOb5WZZqHs3nZiVn5TY1iVk5Ao6mw=kmvBgUFwBw85U64F2V1g@mail.gmail.com' \
--to=juraj.linkes@pantheon.tech \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=ci@dpdk.org \
--cc=nd@arm.com \
--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).