On Sun, Jun 17, 2012 at 11:32:13AM +0800, Royce Lv wrote:
> Guys,
>     Noticed 100+ vdsm processes resides in my system,and all of them in
> sleep status. I guess they're created by the process pool.Little confused
> why we should keep so many vdsm processes alive in the system? Are there
> any user scenario or considerations?

Yes, it is confusing, and yes, it should go with Saggi's

Too bad that that patch is still waiting for some love, verification,
and most probably a rebase. Maybe you can help.

The motivation for this horde of processes is to allow accessing nfs
mounts with no fear of an nfs D state catching the GIL with it. We had
to fork the processes on startup, when the parent is small, or else a
huge memory load is incurred.

vdsm-devel mailing list

Reply via email to