On Fri, May 5, 2023 at 3:38 PM Mike Christie <michael.christie@xxxxxxxxxx> wrote: > > If it's ok to change the behavior of "ps -u root", then we can do this patch: I think this is the right thing to do. Making the user worker threads show up as threads with the vhost process as the parent really seems like a much better model, and more accurate. Yes, they used to show up as random kernel threads, and you'd see them as such (not just for "ps -u root", but simply also with just a normal "ps ax" kind of thing). But that isn't all that helpful, and it's really just annoying to see our kernel threads in "ps ax" output, and I've often wished we didn't do that (it think of all the random "kworker/xyz-kcryptd" etc things that show up). So I think showing them as the threaded children of the vhost process is much nicer, and probably the best option. Because I don't thin kanything is going to get the *old* behavior of showing them as the '[vhost-xyz]' system threads (or whatever the old output ended up being in 'ps ax'), but hopefully nothing wants that horror anyway. At a minimum, the parenting is fundamentally going to look different in the new model. Linus _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linuxfoundation.org/mailman/listinfo/virtualization