From: Manish Katiyar <mkatiyar@gmail.com>
To: Amit Agarwal <amit@amit-agarwal.co.in>
Cc: kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Understanding memory fragmentation in Linux kernel
Date: Sun, 30 Dec 2018 22:22:57 -0800 [thread overview]
Message-ID: <CAE0An6eyNH8TpsGU4Xfz-egwNHX+3E7C+GZuMnu1s8YoY6E9DQ@mail.gmail.com> (raw)
In-Reply-To: <2ef41c8f111a94eaaa6082f6168a56fd@amit-agarwal.co.in>
[-- Attachment #1.1: Type: text/plain, Size: 1143 bytes --]
On Sun, Dec 30, 2018, 10:03 PM Amit Agarwal <amit@amit-agarwal.co.in wrote:
> 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.
>
How do you know it is because of memory ? If you have sufficient RAM then
it should be able to allocate. Does you application fail with ENOMEM ?
Without knowing the error code from application it's hard to suggest
anything.
--
> Thanks,
> -aka
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
[-- Attachment #1.2: Type: text/html, Size: 2227 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2018-12-31 6:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 6:02 Understanding memory fragmentation in Linux kernel Amit Agarwal
2018-12-31 6:22 ` Manish Katiyar [this message]
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=CAE0An6eyNH8TpsGU4Xfz-egwNHX+3E7C+GZuMnu1s8YoY6E9DQ@mail.gmail.com \
--to=mkatiyar@gmail.com \
--cc=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).