-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Barrier request / reply produces memory leak #88
Comments
Hi @KAndrey Would you give us more details about your issue. Thanks, |
Hello, ynkjm.
You can put this code to file "oft/demo/barrier.py" and use following string to execute: After a lot of tests we can see Increase of memory resources usage. This test was made without any traffic. Regards. |
Hi @KAndrey Thanks! |
Hi @KAndrey We have conducted tests in our lab using your OF application. What tool did you use for your test? We need more detail configuration about Lagopus and your environment. Thanks |
Hi, @ynkjm. |
Hi @KAndrey To simplify the problem, we ran an oftest app and a lagopus vswitch separately (on separate hosts). We could not see any change of vmstat on Lagopus, but we saw vmstat changes that you have reported. In our understanding, the memory leak might happen in an oftest side and not in Lagopus vswitch side. If you send us more detail output with Thanks, |
Hi, @ynkjm. |
Hi, we found a bug with pbuf pool re-use case not all ofp message will use the pbuf pool it will use malloc to allocate a new pbuf entry directly then pbuf_free() will add the pbuf to pbuf pool not really release the resource to system use valgrind tool can find the memory usage information maybe can check this part in this issue 2016-07-22 16:52 GMT+08:00 KAndrey [email protected]:
|
The problem as follows. A lot of barrier requests / replies produce memory leak.
The text was updated successfully, but these errors were encountered: