From: Vadim Rozenfeld <vrozenfe@redhat.com>
To: Matthew Frederes <matt@paradisesoftware.net>
Cc: kvm@vger.kernel.org
Subject: Re: hard coded MAX_PHYS_SEGMENTS
Date: Tue, 24 Mar 2015 22:07:24 +1100 [thread overview]
Message-ID: <1427195244.32164.16.camel@oscar> (raw)
In-Reply-To: <65D1AA2D-66E0-4464-B9B4-0626C207B892@paradisesoftware.net>
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
prev parent reply other threads:[~2015-03-24 11:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 7:00 hard coded MAX_PHYS_SEGMENTS Matthew Frederes
2015-03-24 11:07 ` Vadim Rozenfeld [this message]
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=1427195244.32164.16.camel@oscar \
--to=vrozenfe@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=matt@paradisesoftware.net \
/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