From: Michal Hocko <mhocko@suse.com>
To: Pankaj Suryawanshi <suryawanshipankaj@yahoo.com>
Cc: s.szyprowski@samsung.com, mina86@mina86.com, linux-mm@kvack.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: CMA allocation failure and Latency issue
Date: Thu, 7 Mar 2019 09:09:40 +0100 [thread overview]
Message-ID: <20190307080940.GL4603@dhcp22.suse.cz> (raw)
In-Reply-To: <22ed9e4c-962b-4e8c-8549-d8cca578957f@email.android.com>
[Cc linux-mm and lkml]
Please do not use html emails, thanks!
On Thu 07-03-19 13:28:59, Pankaj Suryawanshi wrote:
> Hello,
>
> I am facing issue related to CMA allocation failure of large size buffer.
>
> I am beginner in Linux memory management. So I need your help to debug the
> issue,
>
> I have below questions
>
> 1. Why migration failed
> 2. Who pinned the pages, Which process pinned ,how to know ?
> 3. How to migrate pages forcefully so failure will avoid.(not preferable
> approach)
> etc.
>
> Any help would be appreciated.
>
> Please let me know if you require further information.
>
> Regards,
> Pankaj
--
Michal Hocko
SUSE Labs
parent reply other threads:[~2019-03-07 8:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <22ed9e4c-962b-4e8c-8549-d8cca578957f@email.android.com>]
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=20190307080940.GL4603@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mina86@mina86.com \
--cc=s.szyprowski@samsung.com \
--cc=suryawanshipankaj@yahoo.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