From: Michal Hocko <mhocko@kernel.org>
To: Pankaj Suryawanshi <pankaj.suryawanshi@einfochips.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"minchan@kernel.org" <minchan@kernel.org>,
Kirill Tkhai <ktkhai@virtuozzo.com>
Subject: Re: [External] Re: mm/cma.c: High latency for cma allocation
Date: Mon, 18 Mar 2019 15:29:16 +0100 [thread overview]
Message-ID: <20190318142916.GK8924@dhcp22.suse.cz> (raw)
In-Reply-To: <SG2PR02MB30986F43403B92F31499E42AE8470@SG2PR02MB3098.apcprd02.prod.outlook.com>
On Mon 18-03-19 14:02:09, Pankaj Suryawanshi wrote:
>> > I have the system(vanilla kernel) with 2GB of RAM, reserved 1GB for CMA. No swap or zram.
>> > Sorry, I don't have information where the time is spent.
>> > time is calculated in between cma_alloc call.
>> > I have just cma_alloc trace information/function graph.
>
>> Then please collect that data because it is really hard to judge
>> anything from the numbers you have provided.
>
> Any pointers from which i can get this details ?
I would start by enabling built in tracepoints for the migration or use
a system wide perf monitoring with call graph data.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-03-18 14:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 12:58 Pankaj Suryawanshi
2019-03-18 13:07 ` Michal Hocko
2019-03-18 13:28 ` [External] " Pankaj Suryawanshi
2019-03-18 13:42 ` Michal Hocko
2019-03-18 14:02 ` Pankaj Suryawanshi
2019-03-18 14:29 ` Michal Hocko [this message]
2019-03-19 10:29 ` Pankaj Suryawanshi
2019-03-19 11:45 ` Pankaj Suryawanshi
2019-03-21 9:53 ` Michal Hocko
2019-03-18 13:30 ` Pankaj Suryawanshi
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=20190318142916.GK8924@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=ktkhai@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=pankaj.suryawanshi@einfochips.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