linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Hank Janssen <hjanssen@microsoft.com>
To: Greg KH <gregkh@suse.de>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>,
	"'devel@driverdev.osuosl.org'" <devel@driverdev.osuosl.org>,
	"'virtualization@lists.osdl.org'" <virtualization@lists.osdl.org>,
	"Haiyang Zhang" <haiyangz@microsoft.com>
Subject: RE: [PATCH 5/6] staging: hv: Increased storvsc ringbuffer and max_io_requests
Date: Wed, 4 Aug 2010 03:23:09 +0000	[thread overview]
Message-ID: <8AFC7968D54FB448A30D8F38F259C56223FE59CB@TK5EX14MBXC114.redmond.corp.microsoft.com> (raw)
In-Reply-To: <20100803174005.GC1455@suse.de>


>>And than Greg KH spoke these words:
>>On Tue, Aug 03, 2010 at 05:31:55PM +0000, Hank Janssen wrote:
> >From: Hank Janssen <hjanssen@microsoft.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.


  reply	other threads:[~2010-08-04  3:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03 17:31 [PATCH 5/6] staging: hv: Increased storvsc ringbuffer and max_io_requests Hank Janssen
2010-08-03 17:40 ` Greg KH
2010-08-04  3:23   ` Hank Janssen [this message]
2010-08-04 17:08     ` Greg KH
2010-08-03 17:40 ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8AFC7968D54FB448A30D8F38F259C56223FE59CB@TK5EX14MBXC114.redmond.corp.microsoft.com \
    --to=hjanssen@microsoft.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=haiyangz@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).