Hi Shilpa,
#define ENOBUFS 105 /* No buffer space available */
By any chance are you hitting this issue ?
On Wed, Jul 13, 2016 at 9:30 PM, <kernelnewbies-request@xxxxxxxxxxxxxxxxx> wrote:
Send Kernelnewbies mailing list submissions to
kernelnewbies@xxxxxxxxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
or, via email, send a message with subject or body 'help' to
kernelnewbies-request@xxxxxxxxxxxxxxxxx
You can reach the person managing the list at
kernelnewbies-owner@xxxxxxxxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Kernelnewbies digest..."
Today's Topics:
1. Re: Memory pages not released by the filesystem after a
truncate (Houssem Daoud)
2. Re: Memory pages not released by the filesystem after a
truncate (Houssem Daoud)
3. OS Error: 105 (Shilpa Yellapragada)
4. Re: OS Error: 105 (Rami Rosen)
----------------------------------------------------------------------
Message: 1
Date: Tue, 12 Jul 2016 17:12:31 -0400
From: Houssem Daoud <houssem.daoud@xxxxxxxxxx>
Subject: Re: Memory pages not released by the filesystem after a
truncate
To: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
Cc: kernelnewbies <kernelnewbies@xxxxxxxxxxxxxxxxx>
Message-ID: <ffed6472-b7d5-64d4-3cda-e187b36d583b@xxxxxxxxxx>
Content-Type: text/plain; charset="windows-1252"
The situation is the following: Filesystem anonymous pages are consuming
all the available memory and only 100 MB is left to the system.
The network driver, which allocates memory objects for Jumbo frames,
needs more than 100 MB to run correctly. If a burst of networks packets
arrive together, the available memory is fully consumed and the new
packets start to be dropped.
This situation wouldn't happen if the "useless" pages of the filesystem
were released just after the truncate operation.
What is the point of keeping truncated pages in memory ? Is that a
choice made by the kernel developers or there is something wrong in the
filesystem implementation ?
On 16-07-06 12:29 PM, Mulyadi Santosa wrote:
> Hi
>
> Trying to help here:
> You said you wanna do atomic allocation. But then you said you want to
> allocate around ~100 MB contiguous memory region.
>
> IIRC, if you want to do atomic allocation, usually it can not be that
> big. I am not sure how large, but surely not reaching 100 MB. For that
> size, I think you should rely on vmalloc.
>
> But, for clarification, maybe you should also post your full content
> of /proc/buddyinfo and /proc/meminfo
>
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com <http://the-hydra.blogspot.com>
> training: mulyaditraining.blogspot.com
> <http://mulyaditraining.blogspot.com>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@xxxxxxxxxxxxxxxxx
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160712/c92cf7cd/attachment-0001.html
------------------------------
Message: 2
Date: Tue, 12 Jul 2016 17:16:20 -0400
From: Houssem Daoud <houssem.daoud@xxxxxxxxxx>
Subject: Re: Memory pages not released by the filesystem after a
truncate
To: Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx>
Cc: kernelnewbies <kernelnewbies@xxxxxxxxxxxxxxxxx>
Message-ID: <28d95fdf-967b-9bf3-6854-a5097d5561d7@xxxxxxxxxx>
Content-Type: text/plain; charset="windows-1252"
The situation is as follows:
Filesystem inactive pages are consuming all the available memory and
only 100 MB is left to the system.
The network driver, which allocates memory objects for Jumbo frames,
needs more than 100 MB to run correctly. If a burst of networks packets
arrive together, the available memory is fully consumed and the new
packets are dropped.
This situation wouldn't happen if the "useless" pages of the filesystem
were released just after the truncate operation.
What is the point of keeping truncated pages in memory ? Is that a
choice made by the kernel developers or there is something wrong with
the filesystem implementation ?
On 16-07-06 12:29 PM, Mulyadi Santosa wrote:
> Hi
>
> Trying to help here:
> You said you wanna do atomic allocation. But then you said you want to
> allocate around ~100 MB contiguous memory region.
>
> IIRC, if you want to do atomic allocation, usually it can not be that
> big. I am not sure how large, but surely not reaching 100 MB. For that
> size, I think you should rely on vmalloc.
>
> But, for clarification, maybe you should also post your full content
> of /proc/buddyinfo and /proc/meminfo
>
>
> --
> regards,
>
> Mulyadi Santosa
> Freelance Linux trainer and consultant
>
> blog: the-hydra.blogspot.com <http://the-hydra.blogspot.com>
> training: mulyaditraining.blogspot.com
> <http://mulyaditraining.blogspot.com>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@xxxxxxxxxxxxxxxxx
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20160712/87e8deb5/attachment-0001.html
------------------------------
Message: 3
Date: Wed, 13 Jul 2016 17:50:06 +0530
From: Shilpa Yellapragada <yshilpa.1990@xxxxxxxxx>
Subject: OS Error: 105
To: kernelnewbies@xxxxxxxxxxxxxxxxx
Message-ID:
<CAA1U0b8+8K6C1O0B15qewbz-Cir0YQXj9xqphk1Crpg3B5REkQ@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=UTF-8
Hi,
Can someone explain me why I am encountering an OS error 105, while
trying to write to a socket?
Regards,
Shilpa
--
Shilpa Yellapragada
Software Engineer
Infinera India Pvt Ltd
------------------------------
Message: 4
Date: Wed, 13 Jul 2016 17:43:27 +0300
From: Rami Rosen <roszenrami@xxxxxxxxx>
Subject: Re: OS Error: 105
To: Shilpa Yellapragada <yshilpa.1990@xxxxxxxxx>
Cc: kernelnewbies <kernelnewbies@xxxxxxxxxxxxxxxxx>
Message-ID:
<CAKoUArmq1q3QU0pOYDVQpvi3DHv5rDx_XeTZTmHx7rS+EDU+jw@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset=UTF-8
Hi, Shilpa,
Can you send the code/put it in pastebin and send the link ?
Rami Rosen
On 13 July 2016 at 15:20, Shilpa Yellapragada <yshilpa.1990@xxxxxxxxx> wrote:
> Hi,
>
> Can someone explain me why I am encountering an OS error 105, while
> trying to write to a socket?
>
> Regards,
> Shilpa
>
> --
> Shilpa Yellapragada
> Software Engineer
> Infinera India Pvt Ltd
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@xxxxxxxxxxxxxxxxx
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
------------------------------
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@xxxxxxxxxxxxxxxxx
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
End of Kernelnewbies Digest, Vol 68, Issue 10
*********************************************
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
