Skip to content
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

os/bluestore: reap ioc when stopping aio_thread. #11811

Merged
merged 1 commit into from Nov 9, 2016

Conversation

tanghaodong25
Copy link
Contributor

there is possibillity that reap_ioc don't excute when stopping
aio_thread. so add reap_ioc after aio_thread is stopped.

Signed-off-by: Haodong Tang haodong.tang@intel.com

@liewegas
Copy link
Member

liewegas commented Nov 7, 2016

Did you hit this memory leak in practice? I would be inclined to put reap_ioc() at teh end of _aio_thread() outside of the loop, but either there or where you put it it doesn't help if you set aio_loop while aios are still in flight... which is I think the only case where the leak would happen. To address that, you need to flush before shutting down...

there is possibillity that reap_ioc don't excute when stopping
aio_thread. so add reap_ioc after aio_thread is stopped.

Signed-off-by: Haodong Tang <haodong.tang@intel.com>
@tanghaodong25
Copy link
Contributor Author

@liewegas I'm not sure I understand you correctly, Why are there aios in flight when calling aio_stop? aio finished before ioc is pushed to ioc_reap_queue.

Copy link
Member

@liewegas liewegas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I udnerstand now. Looks good!

@liewegas liewegas merged commit ee3fa76 into ceph:master Nov 9, 2016
@tanghaodong25 tanghaodong25 deleted the reap-ioc-wip branch November 10, 2016 03:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants