[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <SN1PR0301MB166255D26EE1B869200D550BA0350@SN1PR0301MB1662.namprd03.prod.outlook.com>
Date: Thu, 8 Oct 2015 14:40:57 +0000
From: KY Srinivasan <kys@...rosoft.com>
To: Olaf Hering <olaf@...fle.de>
CC: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"apw@...onical.com" <apw@...onical.com>,
"vkuznets@...hat.com" <vkuznets@...hat.com>,
"jasowang@...hat.com" <jasowang@...hat.com>
Subject: RE: [PATCH 01/10] Drivers: hv: util: Increase the timeout for util
services
> -----Original Message-----
> From: Olaf Hering [mailto:olaf@...fle.de]
> Sent: Thursday, October 8, 2015 6:24 AM
> To: KY Srinivasan <kys@...rosoft.com>
> Cc: gregkh@...uxfoundation.org; linux-kernel@...r.kernel.org;
> devel@...uxdriverproject.org; apw@...onical.com; vkuznets@...hat.com;
> jasowang@...hat.com
> Subject: Re: [PATCH 01/10] Drivers: hv: util: Increase the timeout for util
> services
>
> On Wed, Oct 07, K. Y. Srinivasan wrote:
>
> > Util services such as KVP and FCOPY need assistance from daemon's
> running
> > in user space. Increase the timeout so we don't prematurely terminate
> > the transaction in the kernel.
>
> Is this an arbitrary number, or does the host allow such a large delay
> for the response?
Checked with the host guys and it looks like host sets up a 60
second timeout for each transaction and if it times out; it may retry.
Anything below 60 seconds should work for us.
I will add this to the commit log.
K. Y
>
> Olaf
Powered by blists - more mailing lists