All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yongji Xie <xieyongji@bytedance.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Max Gurtovoy <mgurtovoy@nvidia.com>,
	Jason Wang <jasowang@redhat.com>, Jens Axboe <axboe@kernel.dk>,
	Christoph Hellwig <hch@infradead.org>,
	virtualization <virtualization@lists.linux-foundation.org>,
	linux-block@vger.kernel.org
Subject: Re: [PATCH v2] virtio-blk: Remove BUG_ON() in virtio_queue_rq()
Date: Wed, 2 Mar 2022 21:53:17 +0800	[thread overview]
Message-ID: <CACycT3uJFNof7UNTdrEK2dVB-W9q4VVkVWnjos6TJawSRF+EDA@mail.gmail.com> (raw)
In-Reply-To: <20220302083112-mutt-send-email-mst@kernel.org>

On Wed, Mar 2, 2022 at 9:33 PM Michael S. Tsirkin <mst@redhat.com> wrote:
>
> On Wed, Mar 02, 2022 at 03:24:51PM +0200, Max Gurtovoy wrote:
> >
> > On 3/2/2022 3:17 PM, Michael S. Tsirkin wrote:
> > > On Wed, Mar 02, 2022 at 11:51:27AM +0200, Max Gurtovoy wrote:
> > > > On 3/1/2022 5:43 PM, Michael S. Tsirkin wrote:
> > > > > On Mon, Feb 28, 2022 at 02:57:20PM +0800, Xie Yongji wrote:
> > > > > > Currently we have a BUG_ON() to make sure the number of sg
> > > > > > list does not exceed queue_max_segments() in virtio_queue_rq().
> > > > > > However, the block layer uses queue_max_discard_segments()
> > > > > > instead of queue_max_segments() to limit the sg list for
> > > > > > discard requests. So the BUG_ON() might be triggered if
> > > > > > virtio-blk device reports a larger value for max discard
> > > > > > segment than queue_max_segments().
> > > > > Hmm the spec does not say what should happen if max_discard_seg
> > > > > exceeds seg_max. Is this the config you have in mind? how do you
> > > > > create it?
> > > > I don't think it's hard to create it. Just change some registers in the
> > > > device.
> > > >
> > > > But with the dynamic sgl allocation that I added recently, there is no
> > > > problem with this scenario.
> > > Well the problem is device says it can't handle such large descriptors,
> > > I guess it works anyway, but it seems scary.
> >
> > I don't follow.
> >
> > The only problem this patch solves is when a virtio blk device reports
> > larger value for max_discard_segments than max_segments.
> >
>
> No, the peroblem reported is when virtio blk device reports
> max_segments < 256 but not max_discard_segments.
> I would expect discard to follow max_segments restrictions then.
>

I think one point is whether we want to allow the corner case that the
device reports a larger value for max_discard_segments than
max_segments. For example, queue size is 256, max_segments is 128 - 2,
max_discard_segments is 256 - 2.

Thanks,
Yongji

  parent reply	other threads:[~2022-03-02 13:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28  6:57 [PATCH v2] virtio-blk: Remove BUG_ON() in virtio_queue_rq() Xie Yongji
2022-03-01 12:59 ` Christoph Hellwig
2022-03-01 12:59   ` Christoph Hellwig
2022-03-01 15:43 ` Michael S. Tsirkin
2022-03-01 15:43   ` Michael S. Tsirkin
2022-03-02  9:51   ` Max Gurtovoy
2022-03-02 13:17     ` Michael S. Tsirkin
2022-03-02 13:17       ` Michael S. Tsirkin
2022-03-02 13:24       ` Max Gurtovoy
2022-03-02 13:33         ` Michael S. Tsirkin
2022-03-02 13:33           ` Michael S. Tsirkin
2022-03-02 13:45           ` Max Gurtovoy
2022-03-02 14:15             ` Michael S. Tsirkin
2022-03-02 14:15               ` Michael S. Tsirkin
2022-03-02 14:27               ` Max Gurtovoy
2022-03-02 14:48                 ` Michael S. Tsirkin
2022-03-02 14:48                   ` Michael S. Tsirkin
2022-03-02 13:53           ` Yongji Xie [this message]
2022-03-02 14:20             ` Michael S. Tsirkin
2022-03-02 14:20               ` Michael S. Tsirkin
2022-03-02 10:46   ` Yongji Xie
2022-03-02 13:15     ` Michael S. Tsirkin
2022-03-02 13:15       ` Michael S. Tsirkin
2022-03-02 15:05       ` Max Gurtovoy
2022-03-03  3:31         ` Yongji Xie
2022-03-03  7:22           ` Michael S. Tsirkin
2022-03-03  7:22             ` Michael S. Tsirkin
2022-03-03  8:11             ` Yongji Xie

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=CACycT3uJFNof7UNTdrEK2dVB-W9q4VVkVWnjos6TJawSRF+EDA@mail.gmail.com \
    --to=xieyongji@bytedance.com \
    --cc=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=jasowang@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=mgurtovoy@nvidia.com \
    --cc=mst@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.