From: Nava kishore Manne <nava.kishore.manne@amd.com>
To: <mdf@kernel.org>, <hao.wu@intel.com>, <yilun.xu@intel.com>,
<trix@redhat.com>, <sumit.semwal@linaro.org>,
<christian.koenig@amd.com>, <linux-fpga@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-media@vger.kernel.org>,
<dri-devel@lists.freedesktop.org>,
<linaro-mm-sig@lists.linaro.org>
Subject: [RFC 0/2]fpga: Add fpga configuration support from a pre-allocated dma-able buffer
Date: Wed, 22 Nov 2023 11:00:33 +0530 [thread overview]
Message-ID: <20231122053035.3758124-1-nava.kishore.manne@amd.com> (raw)
Lots of embedded systems have memory constraints but they need to load
very large configuration files.The FPGA subsystem allows drivers to
request this configuration image be loaded from the filesystem,but this
requires that the entire configuration data be loaded into kernel memory
first before it's provided to the driver.This can lead to a situation where
we map the configuration data twice, once to load the configuration data
into kernel memory and once to copy the configuration data into the final
resting place which is nothing but a dma-able continuous buffer.
This creates needless memory pressure and delays due to multiple copies.
Let's add a dmabuf handling support to the fpga manager framework that
allows drivers to load the Configuration data directly from a pre-allocated
buffer. This skips the intermediate step of allocating a buffer in kernel
memory to hold the Configuration data.
This implementation allows the lower-level drivers to request the FPGA
Configuration image be loaded from pre-allocated dma-able continuous
buffer and also it avoid needless memory pressure and delays due to
multiple copies.
Please take a look at the changes and let us know if any improvements
are required.
Nava kishore Manne (2):
fpga: support loading from a pre-allocated buffer
fpga: versal: Use the scatterlist interface
drivers/fpga/fpga-mgr.c | 113 ++++++++++++++++++++++++++++++++++
drivers/fpga/versal-fpga.c | 13 ++++
include/linux/fpga/fpga-mgr.h | 10 +++
3 files changed, 136 insertions(+)
--
2.25.1
next reply other threads:[~2023-11-22 5:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 5:30 Nava kishore Manne [this message]
2023-11-22 5:30 ` [RFC 1/2] fpga: support loading from a pre-allocated buffer Nava kishore Manne
2024-01-15 17:08 ` Marco Pagani
2023-11-22 5:30 ` [RFC 2/2] fpga: versal: Use the scatterlist interface Nava kishore Manne
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=20231122053035.3758124-1-nava.kishore.manne@amd.com \
--to=nava.kishore.manne@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=hao.wu@intel.com \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=sumit.semwal@linaro.org \
--cc=trix@redhat.com \
--cc=yilun.xu@intel.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 read-only IMAP folder(s) and NNTP newsgroup(s).