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

Excessive number of "bioset" kernel processes in 4.4 kernel #1427

Closed
ncguk opened this issue Apr 23, 2016 · 4 comments

Comments

@ncguk
Copy link

commented Apr 23, 2016

Since upgrading to kernel 4.4.7 (and now 4.4.8) on an otherwise stock 2016-03-18-raspbian-jessie-lite I have 25 kernel processes named bioset showing in top output, each with a nice priority of -20, e.g.:

60 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 bioset

This happens on an RPi B+, RPi2 and RPi3, all run headless. As I didn't see this on the 4.1 kernel, am I to assume this is not desired behaviour?

@popcornmix

This comment has been minimized.

Copy link
Collaborator

commented Apr 23, 2016

Seems like a kernel working thread involved in block I/O. See:
https://answers.launchpad.net/ubuntu/+question/272922

I don't think there is any issue. It takes no CPU when it is not in use.

@ncguk

This comment has been minimized.

Copy link
Author

commented Apr 23, 2016

It's true they don't seem to consume CPU or RAM. It's odd, though, isn't it, that they weren't there in 4.1 and now are in 4.4?

@popcornmix

This comment has been minimized.

Copy link
Collaborator

commented Apr 23, 2016

That is a decision the upstream kernel developers have taken.
If you search around for bioset you can see these kernel threads are present on all platforms with newer kernels. I can find no evidence that there is a problem with that.

@ncguk

This comment has been minimized.

Copy link
Author

commented Apr 23, 2016

Fair enough. I'll close the ticket.

@ncguk ncguk closed this Apr 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.