All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Joerg Roedel <joro@8bytes.org>, Jason Wang <jasowang@redhat.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Jens Axboe <axboe@kernel.dk>,
	virtualization@lists.linux-foundation.org,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	iommu@lists.linux-foundation.org, jfehlig@suse.com,
	jon.grimm@amd.com, brijesh.singh@amd.com, jroedel@suse.de,
	pbonzini@redhat.com, jsnow@redhat.com
Subject: Re: [PATCH 5/5] virtio-blk: Consider virtio_max_dma_size() for maximum segment size
Date: Wed, 23 Jan 2019 17:25:00 -0500	[thread overview]
Message-ID: <20190123170850-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20190123213139.GD9032@lst.de>

On Wed, Jan 23, 2019 at 10:31:39PM +0100, Christoph Hellwig wrote:
> On Wed, Jan 23, 2019 at 05:30:49PM +0100, Joerg Roedel wrote:
> > +	max_size = virtio_max_dma_size(vdev);
> > +
> >  	/* Host can optionally specify maximum segment size and number of
> >  	 * segments. */
> >  	err = virtio_cread_feature(vdev, VIRTIO_BLK_F_SIZE_MAX,
> >  				   struct virtio_blk_config, size_max, &v);
> >  	if (!err)
> > -		blk_queue_max_segment_size(q, v);
> > -	else
> > -		blk_queue_max_segment_size(q, -1U);
> > +		max_size = min(max_size, v);
> > +
> > +	blk_queue_max_segment_size(q, max_size);
> 
> I wonder if we should just move the dma max segment size check
> into blk_queue_max_segment_size so that all block drivers benefit
> from it.  Even if not I think at least the SCSI midlayer should
> be updated to support it.
> 
> Btw, I wonder why virtio-scsi sticks to the default segment size,
> unlike virtio-blk.

Well no one bothered exposing that through that device.
Why does virtio block have it? Hard for me to say. First driver version
had it already but QEMU does not seem to use it and it seems that it
never did.


-- 
MST

  parent reply	other threads:[~2019-01-23 22:25 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-23 16:30 [PATCH 0/5 v3] Fix virtio-blk issue with SWIOTLB Joerg Roedel
2019-01-23 16:30 ` [PATCH 1/5] swiotlb: Introduce swiotlb_max_mapping_size() Joerg Roedel
2019-01-23 16:30 ` Joerg Roedel
2019-01-23 21:28   ` Christoph Hellwig
2019-01-23 21:28     ` Christoph Hellwig
2019-01-24  8:24     ` Joerg Roedel
2019-01-24  8:47       ` Christoph Hellwig
2019-01-24  8:47       ` Christoph Hellwig
2019-01-24  8:24     ` Joerg Roedel
2019-01-23 21:28   ` Christoph Hellwig
2019-01-23 16:30 ` [PATCH 2/5] swiotlb: Add is_swiotlb_active() function Joerg Roedel
2019-01-23 16:30 ` Joerg Roedel
2019-01-23 21:27   ` Christoph Hellwig
2019-01-23 21:27   ` Christoph Hellwig
2019-01-24  8:29     ` Joerg Roedel
2019-01-24  8:29     ` Joerg Roedel
2019-01-24  8:41       ` Christoph Hellwig
2019-01-24  8:41       ` Christoph Hellwig
2019-01-24  8:41         ` Christoph Hellwig
2019-01-24 15:00         ` Joerg Roedel
2019-01-28 17:19           ` Michael S. Tsirkin
2019-01-28 17:19           ` Michael S. Tsirkin
2019-01-24 15:00         ` Joerg Roedel
2019-01-23 16:30 ` [PATCH 3/5] dma: Introduce dma_max_mapping_size() Joerg Roedel
2019-01-23 16:30 ` Joerg Roedel
2019-01-23 21:29   ` Christoph Hellwig
2019-01-23 21:29   ` Christoph Hellwig
2019-01-23 16:30 ` [PATCH 4/5] virtio: Introduce virtio_max_dma_size() Joerg Roedel
2019-01-23 16:30 ` Joerg Roedel
2019-01-23 16:30 ` [PATCH 5/5] virtio-blk: Consider virtio_max_dma_size() for maximum segment size Joerg Roedel
2019-01-23 16:30 ` Joerg Roedel
2019-01-23 21:31   ` Christoph Hellwig
2019-01-23 22:25     ` Michael S. Tsirkin
2019-01-23 22:25     ` Michael S. Tsirkin [this message]
2019-01-24  8:40     ` Joerg Roedel
2019-01-24  8:42       ` Christoph Hellwig
2019-01-24  8:42       ` Christoph Hellwig
2019-01-24  9:51         ` Joerg Roedel
2019-01-24  9:51           ` Joerg Roedel
2019-01-28  8:05           ` Christoph Hellwig
2019-01-28 17:14             ` Michael S. Tsirkin
2019-01-28 17:14             ` Michael S. Tsirkin
2019-01-29  7:38               ` Christoph Hellwig
2019-01-29  7:38               ` Christoph Hellwig
2019-01-28  8:05           ` Christoph Hellwig
2019-01-24  9:51         ` Joerg Roedel
2019-01-24  8:40     ` Joerg Roedel
2019-01-23 21:31   ` Christoph Hellwig
2019-01-23 17:09 ` [PATCH 0/5 v3] Fix virtio-blk issue with SWIOTLB Konrad Rzeszutek Wilk
2019-01-23 17:09 ` Konrad Rzeszutek Wilk
2019-01-23 18:51 ` Michael S. Tsirkin
2019-01-23 18:51 ` Michael S. Tsirkin
2019-01-23 21:14   ` Konrad Rzeszutek Wilk
2019-01-28 15:20     ` Michael S. Tsirkin
2019-01-28 15:53       ` Konrad Rzeszutek Wilk
2019-01-28 15:53         ` Konrad Rzeszutek Wilk
2019-01-28 15:53       ` Konrad Rzeszutek Wilk
2019-01-28 15:20     ` Michael S. Tsirkin
2019-01-23 21:14   ` Konrad Rzeszutek Wilk
2019-01-29  8:43 [PATCH 0/5 v4] " Joerg Roedel
2019-01-29  8:43 ` [PATCH 5/5] virtio-blk: Consider virtio_max_dma_size() for maximum segment size Joerg Roedel
2019-01-29 17:13   ` Christoph Hellwig
2019-01-29 17:13   ` Christoph Hellwig
2019-01-29  8:43 ` Joerg Roedel
2019-01-30 16:40 [PATCH 0/5 v5] Fix virtio-blk issue with SWIOTLB Joerg Roedel
2019-01-30 16:40 ` [PATCH 5/5] virtio-blk: Consider virtio_max_dma_size() for maximum segment size Joerg Roedel
2019-01-30 16:40 ` Joerg Roedel
2019-01-31 16:33 [PATCH 0/5 v6] Fix virtio-blk issue with SWIOTLB Joerg Roedel
2019-01-31 16:34 ` [PATCH 5/5] virtio-blk: Consider virtio_max_dma_size() for maximum segment size Joerg Roedel
2019-01-31 16:34 ` Joerg Roedel

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=20190123170850-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=brijesh.singh@amd.com \
    --cc=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jasowang@redhat.com \
    --cc=jfehlig@suse.com \
    --cc=jon.grimm@amd.com \
    --cc=joro@8bytes.org \
    --cc=jroedel@suse.de \
    --cc=jsnow@redhat.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --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.