[ovirt-devel] [VDSM][sampling] thread pool status and handling of stuck calls
Nir Soffer
nsoffer at redhat.com
Mon Jul 7 15:42:25 UTC 2014
----- Original Message -----
> From: "Michal Skrivanek" <mskrivan at redhat.com>
> To: "Nir Soffer" <nsoffer at redhat.com>
> Cc: "Francesco Romani" <fromani at redhat.com>, devel at ovirt.org, "Federico Simoncelli" <fsimonce at redhat.com>, "Adam
> Litke" <alitke at redhat.com>
> Sent: Monday, July 7, 2014 6:04:19 PM
> Subject: Re: [ovirt-devel] [VDSM][sampling] thread pool status and handling of stuck calls
>
>
> On Jul 7, 2014, at 16:53 , Nir Soffer <nsoffer at redhat.com> wrote:
> > If we separate storage calls so vm sampling continue even if storage
> > cause qemu to block - do we gain anything? I guess this vm is
> > not useful if its storage is not available, and will soon will
> > pause anyway.
> >
> > Looks like the simplest solution is the best and fancy separation
> > of sampling calls is needed.
>
> you meant "not needed", no?
Yes, not needed.
More information about the Devel
mailing list