From: Ekansh Gupta <quic_ekangupt@quicinc.com>
To: <srinivas.kandagatla@linaro.org>, <linux-arm-msm@vger.kernel.org>
Cc: Ekansh Gupta <quic_ekangupt@quicinc.com>,
<ekangupt@qti.qualcomm.com>, <gregkh@linuxfoundation.org>,
<linux-kernel@vger.kernel.org>,
<fastrpc.upstream@qti.qualcomm.com>, <quic_anane@quicinc.com>
Subject: [PATCH v1 0/2] Add changes for cached buffer and persistent header buffers
Date: Fri, 9 Jun 2023 16:09:45 +0530 [thread overview]
Message-ID: <1686307187-15199-1-git-send-email-quic_ekangupt@quicinc.com> (raw)
This patch series carries changes to reduce RPC call overhead by
skippikng DMA API allocation calls for all type of buffer allocation
requests.
Cached buffer support enables caching of allocated buffers
instead of freeing which can be reused for any new request.
Persistent header buffer changes allocated a number for header
buffers during CDSP process initialization which is then used
for remote calls by the process.
When any process make a remote call, the metadata buffer is first
tried to be used from allocated persistent header buffers. If due
to any reason, persistent header buffers are not available, the
allocation request falls back to cached buffers and allocations
using DMA API.
Ekansh Gupta (2):
misc: fastrpc: Add cached buffer support
misc: fastrpc: Add persistent header buffer support
drivers/misc/fastrpc.c | 348 ++++++++++++++++++++++++++++++++++++--------
include/uapi/misc/fastrpc.h | 8 +
2 files changed, 295 insertions(+), 61 deletions(-)
--
2.7.4
next reply other threads:[~2023-06-09 10:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 10:39 Ekansh Gupta [this message]
2023-06-09 10:39 ` [PATCH v1 1/2] misc: fastrpc: Add cached buffer support Ekansh Gupta
2023-06-12 12:55 ` Srinivas Kandagatla
2023-06-09 10:39 ` [PATCH v1 2/2] misc: fastrpc: Add persistent header " Ekansh Gupta
2023-06-09 18:13 ` kernel test robot
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=1686307187-15199-1-git-send-email-quic_ekangupt@quicinc.com \
--to=quic_ekangupt@quicinc.com \
--cc=ekangupt@qti.qualcomm.com \
--cc=fastrpc.upstream@qti.qualcomm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_anane@quicinc.com \
--cc=srinivas.kandagatla@linaro.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 read-only IMAP folder(s) and NNTP newsgroup(s).