From mboxrd@z Thu Jan 1 00:00:00 1970 From: Vadim Rozenfeld Subject: Re: hard coded MAX_PHYS_SEGMENTS Date: Tue, 24 Mar 2015 22:07:24 +1100 Message-ID: <1427195244.32164.16.camel@oscar> References: <65D1AA2D-66E0-4464-B9B4-0626C207B892@paradisesoftware.net> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Matthew Frederes Return-path: Received: from mx1.redhat.com ([209.132.183.28]:54541 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751814AbbCXLH3 (ORCPT ); Tue, 24 Mar 2015 07:07:29 -0400 In-Reply-To: <65D1AA2D-66E0-4464-B9B4-0626C207B892@paradisesoftware.net> Sender: kvm-owner@vger.kernel.org List-ID: On Tue, 2015-03-24 at 02:00 -0500, Matthew Frederes wrote: > Hello, > > I would like to see MAX_PHYS_SEGMENTS as seen hard coded to 64 in virtio_stor.h increased, in order to get better throughput when using an LTO tape drive attached to the host SCSI adapter from within a 64-bit version of Windows Server. The tape drive supports a MaxBlock of 16,777,215. > > Before I attempt to develop a patch I wanted to discuss here on this listserv... > > Thank you, > > Matthew D. Frederes > Business Information Technologies, Inc. > Hello Matthew, It shouldn't be a problem to increase MAX_PHYS_SEGMENTS, NumberOfPhysicalBreaks will be updated accordingly. Vadim. > > > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html