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.

Sign up for GitHub

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

Jump to bottom

LinitD uses a full CPU core #4

Open
niaow opened this issue Jan 9, 2018 · 1 comment
Open

LinitD uses a full CPU core #4

niaow opened this issue Jan 9, 2018 · 1 comment
Labels
bug

Comments

@niaow
Copy link
Member

niaow commented Jan 9, 2018 •
edited
Loading

The CPU usage is always a full core. And in QEMU, it brings the system to 100% CPU. I think my low epoll timeout is causing way too many context switches. If I dynamically adjust the timing, I should be able to cut back the usage.
@niaow niaow added the bug label Jan 9, 2018
@niaow niaow changed the title LinitD uses way too much CPU LinitD uses a full CPU core Jan 9, 2018
@niaow
Copy link
Member Author

niaow commented Jan 9, 2018

This is apparently not the error: epoll seems to get stuck sending us EPOLLIN, but we read 0 bytes with read. Not really sure what is going on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@niaow