search

mos-stack / mOS-networking-stack

A Specialized Network Programming Library for Stateful Middleboxes:
http://mos.kaist.edu
Other
103 stars 21 forks source link

Issue with running sample application using > 2 cores. #8

Closed koolzz closed 7 years ago

koolzz commented 7 years ago

Hi, I'm trying to run sample epserver with 8 cores but it stops working without an error message. At times it prints the first stat print dump but stops after that. When only given 2 cores the sample epserver works perfectly fine. I'm also succesfull at running epwget with 8 cores.

Moreover, I'm able to run the mtcp epserver (https://github.com/eunyoung14/mtcp) on the same machine with any number of cores without an issue. But when using it I received a large number of HANDLE_TCP_ST_CLOSING:1133 NOT ACK errors when testing it with large number of total_flows in epwget. But the mOS sample epserver running with 2 cores doesn't give me that error with the same test run.

image

Running it with gdb I can see the new thread creation messages and then all of them simply exit.

image

I was hoping you can help me figure this out. Which information do you need from me? I was using the generated mos config and following the standard install instructions for dpdk setup from here http://mos.kaist.edu/guide/walkthrough/03_setup.html#compile-and-build-mos-net-library-with-dpdk

Sincerely, Nick

ajamshed commented 7 years ago

Hi,

Can you please check your dmesg log? It looks like you may be facing OOM (out of memory) issues. How much RAM does your system have? You can try reducing mOS stack's memory fingerprint by reducing the max_concurrency limit to a lower value.

kyoungsoo commented 7 years ago

Hi Asim,

You are talking about OOM of kernel. Well, I think it is better to warn the user if it allocates too much memory at start out of all physical memory. That way, the user could develop a better idea why it crashes.

--KyoungSoo

2017년 6월 11일 (일) 오전 8:03, Asim Jamshed notifications@github.com님이 작성:

Hi,

Can you please check your dmesg log? It looks like you may be facing OOM (out of memory) issues. How much RAM does your system have? You can try reducing mOS stack's memory fingerprint by reducing the max_concurrency limit to a lower value.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/ndsl-kaist/mOS-networking-stack/issues/8#issuecomment-307595220, or mute the thread https://github.com/notifications/unsubscribe-auth/ASuKZ5TOf4dNegiYU9foeQUKyMA7N8edks5sCyDNgaJpZM4N2Owd .

koolzz commented 7 years ago

@ajamshed Thanks for the quick response, this was exactly the cause of my issue. I'm running 16 GB or ram, after reducing the max_concurrency to 10000 everything works.