staging: hv: Increased storvsc ringbuffer and max_io_requests
in [Kernel]
|
Prev: [tip:x86/cpu] x86, cpu: RDC doesn't have CPUID, which is what c_ident is
Next: staging: hv: Fixed the value of the 64bit-hole inside ring buffer
From: Greg KH on 3 Aug 2010 13:50 On Tue, Aug 03, 2010 at 05:31:55PM +0000, Hank Janssen wrote: > From: Hank Janssen <hjanssen(a)microsoft.com> > > Increased storvsc ringbuffer and max_io_requests. This now more closely mimics > the numbers on Hyper-V. And will allow more IO requests to take place for the SCSI driver. > > Signed-off-by:Hank Janssen <hjanssen(a)microsoft.com> > Signed-off-by:Haiyang Zhang <haiyangz(a)microsoft.com> Again with the trailing spaces :( -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Greg KH on 3 Aug 2010 13:50 On Tue, Aug 03, 2010 at 05:31:55PM +0000, Hank Janssen wrote: > From: Hank Janssen <hjanssen(a)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? > 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? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Hank Janssen on 3 Aug 2010 23:30 >>And than Greg KH spoke these words: >>On Tue, Aug 03, 2010 at 05:31:55PM +0000, Hank Janssen wrote: > >From: Hank Janssen <hjanssen(a)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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Greg KH on 4 Aug 2010 13:20
On Wed, Aug 04, 2010 at 03:23:09AM +0000, Hank Janssen wrote: > > >>And than Greg KH spoke these words: > >>On Tue, Aug 03, 2010 at 05:31:55PM +0000, Hank Janssen wrote: > > >From: Hank Janssen <hjanssen(a)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. All good, care to included this in the changelog comment when you resend this whole series? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |