All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
	Anthony Liguori <aliguori@us.ibm.com>,
	virtualization@lists.linux-foundation.org,
	Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [PATCH 1/2] virtio: block: set max_segment_size and max_sectors to infinite.
Date: Wed, 3 Dec 2008 10:43:21 -0800	[thread overview]
Message-ID: <20081203184321.GC19628@sequoia.sous-sol.org> (raw)
In-Reply-To: <200811171724.15682.rusty@rustcorp.com.au>

* Rusty Russell (rusty@rustcorp.com.au) wrote:
> Setting max_segment_size allows more than 64k per sg element, unless
> the host specified a limit.  Setting max_sectors indicates that our
> max_hw_segments is the only limit.

We had been using a simple hardocded constant to increase max sectors to
improve throughput.  This (along with 2/2) are tested and showing nice numbers.

Acked-by: Chris Wright <chrisw@sous-sol.org>

      parent reply	other threads:[~2008-12-03 18:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200811141215.33950.rusty@rustcorp.com.au>
     [not found] ` <20081114093023.GQ26778@kernel.dk>
2008-11-17  6:52   ` [PATCH RFC] virtio: use QUEUE_FLAG_CLUSTER in virtio_blk Rusty Russell
2008-11-17  6:54     ` [PATCH 1/2] virtio: block: set max_segment_size and max_sectors to infinite Rusty Russell
2008-11-17  7:04       ` [PATCH 2/2] virtio: block: dynamic maximum segments Rusty Russell
2008-11-26 17:42       ` [PATCH 1/2] virtio: block: set max_segment_size and max_sectors to infinite Chris Wright
2008-11-27 13:00         ` Rusty Russell
2008-11-27 13:04           ` Jens Axboe
2008-12-03 18:43       ` Chris Wright [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=20081203184321.GC19628@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=aliguori@us.ibm.com \
    --cc=jens.axboe@oracle.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=rusty@rustcorp.com.au \
    --cc=virtualization@lists.linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.