From: Pankaj Suryawanshi <pankaj.suryawanshi@einfochips.com>
To: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "minchan@kernel.org" <minchan@kernel.org>,
Michal Hocko <mhocko@kernel.org>
Subject: High Latency of CMA allocation
Date: Fri, 15 Mar 2019 09:49:26 +0000 [thread overview]
Message-ID: <SG2PR02MB30984EA8472065757E5F32F7E8440@SG2PR02MB3098.apcprd02.prod.outlook.com> (raw)
Hello,
I am facing issue of high latency in CMA allocation of large size buffer .
I am frequently allocating/deallocation CMA memory, but latency of allocation is very high.
Below are the stat for allocation/deallocation latency issue.
(389120 kB), latency 29997 us
(389120 kB), latency 22957 us
(389120 kB), latency 25735 us
(389120 kB), latency 12736 us
(389120 kB), latency 26009 us
(389120 kB), latency 18058 us
(389120 kB), latency 27997 us
(16 kB), latency 560 us
(256 kB), latency 280 us
(4 kB), latency 311 us
Is there any workaround or solution for this(cma_alloc latency) issue ?
Regards,
Pankaj
************************************************************************************************************************************************************* eInfochips Business Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated. Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. *************************************************************************************************************************************************************
reply other threads:[~2019-03-15 9:49 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=SG2PR02MB30984EA8472065757E5F32F7E8440@SG2PR02MB3098.apcprd02.prod.outlook.com \
--to=pankaj.suryawanshi@einfochips.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=minchan@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).