[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <8AFC7968D54FB448A30D8F38F259C56223FE59CB@TK5EX14MBXC114.redmond.corp.microsoft.com>
Date: Wed, 4 Aug 2010 03:23:09 +0000
From: Hank Janssen <hjanssen@...rosoft.com>
To: Greg KH <gregkh@...e.de>
CC: "'linux-kernel@...r.kernel.org'" <linux-kernel@...r.kernel.org>,
"'devel@...verdev.osuosl.org'" <devel@...verdev.osuosl.org>,
"'virtualization@...ts.osdl.org'" <virtualization@...ts.osdl.org>,
"Haiyang Zhang" <haiyangz@...rosoft.com>
Subject: RE: [PATCH 5/6] staging: hv: Increased storvsc ringbuffer and
max_io_requests
>>And than Greg KH spoke these words:
>>On Tue, Aug 03, 2010 at 05:31:55PM +0000, Hank Janssen wrote:
> >From: Hank Janssen <hjanssen@...rosoft.com>
> >
> >Increased storvsc ringbuffer and max_io_requests. This now more
> >closely mimics the numbers on Hyper-V.
>
>What do you mean by this? The max provided by the hypervisor?
Max_IO is set to double from what it was before, Hyper-V allows it and
We have had appliance builder requests to see if it was a problem to increase
The number.
Ringbuffer size for storvsc is now increased because I have seen
A few buffer problems on extremely busy systems. They where
Set pretty low before. And since max_io_requests is increased I
Really needed to increase the buffer as well.
>> And will allow more IO requests to take place for the SCSI driver.
>
>Which means what, better throughput? Or just more outstanding requests and the same speed overall?
It means better throughput of high load systems, else you get buffer
Contention.
Thanks,
Hank.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists