kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
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:54:00 -0800	[thread overview]
Message-ID: <CAE0An6dWRPOKBMDKOhP9u_FeJbGA0UMTWoBSCjnL6VYz0gqHXg@mail.gmail.com> (raw)
In-Reply-To: <5ac059b588692de67b6eeede673ae5b2@amit-agarwal.co.in>


[-- Attachment #1.1: Type: text/plain, Size: 931 bytes --]

On Sun, Dec 30, 2018, 10:28 PM Amit Agarwal <amit@amit-agarwal.co.in wrote:

> On 2018-12-31 06:22, Manish Katiyar wrote:
>
>
> 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.
>
>
> There is no debugging enabled on site and there is nothing we can do now
> to enable it and it is happening in only one site. But from whatever logs I
> have, it is failing in calloc.
>
> I am not requesting help in resolving the issue with application (I will
> be able to debug that), but only need help in understanding the memory
> fragmentation part. ( I gave details of original problem so that I can
> explain what I am trying to understand and wh
>

Maybe you can try

echo m > /proc/sysrq-trigger


Or looking at /proc/buddyinfo



>
> --
> Thanks,
> -aka
>

[-- Attachment #1.2: Type: text/html, Size: 2726 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

  reply	other threads:[~2018-12-31  6:54 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
2018-12-31  6:28   ` Amit Agarwal
2018-12-31  6:54     ` Manish Katiyar [this message]
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=CAE0An6dWRPOKBMDKOhP9u_FeJbGA0UMTWoBSCjnL6VYz0gqHXg@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).