• State Accepted Answer
  • Locked Locked
  • Replies 6 replies
  • Subscribers 24 subscribers
  • Views 4235 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

BSD send() => BSD_ENOMEM

Galuski

Hi,

I'm actually implementing a webserver with multiple threads and sockets listening to port 80.

The MDK is version 5.29.

Assuming the BSD send() can be called from different threads for different sockets, I don't understand the return value BSD_ENOMEM, which I sometimes get.

All these error return values are not really described in detail. "Not enough memory" for BSD_ENOMEM is not really helpful.

  • Which memory got low?
    I tried to play with the Ethernet core memory (NET_MEM_POOL_SIZE), the heap and all involved stack sizes of the KEIL driver.
    No luck. Can't get rid of this error.

It does not happen very often. Let's say 1 out of 5000 send() calls.

It happens in blocking & non-blocking mode.

Any help is appreciated.

Michael

Parents
  • 0 in reply to Franc Urbanc

    Hi Frank!

    First let me thank you for your complete and professional answer! I really appreciate it.

    • I forgot to mention that our webserver is from Segger.
    • I was assuming that the involved memory buffer is the net mem pool and I already played with the size.
      But also increasing the buffer to 60k didn't solve the problem.
      Instead I discovered a strange behavior of the enabled DHCP client: With some big values of the buffer size, the DHCP client didn't receive an IP address anymore (netDHCP_Notify() wasn't triggered anymore). But that is going to be subject of another post ;-)
    • I'm going to obey your tips with the task handling functions and give you feedback.
    • "Sending smaller blocks": Do you suggest sizing down the maximal TCP segment size or a manual segmentation on my side before I give the data to the send() function?

    Again thanks for the help.

    Michael
    Pittsburgh, USA

Reply
  • 0 in reply to Franc Urbanc

    Hi Frank!

    First let me thank you for your complete and professional answer! I really appreciate it.

    • I forgot to mention that our webserver is from Segger.
    • I was assuming that the involved memory buffer is the net mem pool and I already played with the size.
      But also increasing the buffer to 60k didn't solve the problem.
      Instead I discovered a strange behavior of the enabled DHCP client: With some big values of the buffer size, the DHCP client didn't receive an IP address anymore (netDHCP_Notify() wasn't triggered anymore). But that is going to be subject of another post ;-)
    • I'm going to obey your tips with the task handling functions and give you feedback.
    • "Sending smaller blocks": Do you suggest sizing down the maximal TCP segment size or a manual segmentation on my side before I give the data to the send() function?

    Again thanks for the help.

    Michael
    Pittsburgh, USA

Children
No data