From: Amit Agarwal <amit@amit-agarwal.co.in>
To: kernelnewbies@kernelnewbies.org
Subject: Understanding memory fragmentation in Linux kernel
Date: Mon, 31 Dec 2018 06:02:24 +0000 [thread overview]
Message-ID: <2ef41c8f111a94eaaa6082f6168a56fd@amit-agarwal.co.in> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 624 bytes --]
Hi All,
I am trying to understand memory fragmentation and how to understand
and/or analyze the same.
Is there some detailed documentation on pagetypeinfo and buddyinfo files
present in the proc directory? Am I looking at right files to understand
if the memory is fragmented.
Problem Description:
One of the applications does a few 200-300Mb calloc's during start-up.
On one of the production servers, the application does not start up
although there should be enough RAM available for application to start.
I am suspecting that this is because of fragmentation and would like to
confirm the same.
--
Thanks,
-aka
[-- Attachment #1.2: Type: text/html, Size: 966 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2018-12-31 6:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 6:02 Amit Agarwal [this message]
2018-12-31 6:22 ` Understanding memory fragmentation in Linux kernel Manish Katiyar
2018-12-31 6:28 ` Amit Agarwal
2018-12-31 6:54 ` Manish Katiyar
2018-12-31 7:14 ` Amit Agarwal
2019-01-13 18:36 ` Richard Siegfried
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=2ef41c8f111a94eaaa6082f6168a56fd@amit-agarwal.co.in \
--to=amit@amit-agarwal.co.in \
--cc=kernelnewbies@kernelnewbies.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).