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