From: Patryk <pbiel7@gmail.com>
To: linux-fpga@vger.kernel.org
Subject: FPGA-HPS DDR contention on Agilex5 SoC while running Linux
Date: Tue, 19 Aug 2025 14:28:28 +0200 [thread overview]
Message-ID: <CA+DkFDbzx+0CJVjdOGkah3amqZ8VHE6_-e-eq03-QT3bB0DSVw@mail.gmail.com> (raw)
Hi
I’m working on a device based on an Agilex5 SoC with HPS, which is new
hardware for me.
I've been considering the following scenario: the FPGA and HPS will
share DDR memory, and Linux is running on the HPS at the same time.
The FPGA will be streaming a high volume of data that needs to be
consumed by a userspace program on the CPU.
I’m concerned that if the FPGA saturates the memory interconnect, the
kernel might struggle to perform memory allocations or other
transactions for other threads.
Has anyone encountered this kind of bus contention on Agilex/SoC
platforms? What strategies do you use to prevent FPGA traffic from
starving HPS memory accesses while Linux is running? Also, is there
any recommendation / strategy for an FPGA and a userspace program on
Linux to exchange data efficiently and safely in this kind of setup?
I don't expect in-depth answers, and will be grateful for anything
that will channel me in the right direction.
Best regards
Patryk
reply other threads:[~2025-08-19 12:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CA+DkFDbzx+0CJVjdOGkah3amqZ8VHE6_-e-eq03-QT3bB0DSVw@mail.gmail.com \
--to=pbiel7@gmail.com \
--cc=linux-fpga@vger.kernel.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).