From: Tiwei Bie <tiwei.bie@intel.com>
To: Jason Wang <jasowang@redhat.com>
Cc: mst@redhat.com, virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
wexu@redhat.com, jfreimann@redhat.com
Subject: Re: [RFC v4 3/5] virtio_ring: add packed ring support
Date: Mon, 21 May 2018 10:39:44 +0800 [thread overview]
Message-ID: <20180521023944.GA16702@debian> (raw)
In-Reply-To: <b8c0d147-2711-cb26-a084-e7d3d32d0002@redhat.com>
On Mon, May 21, 2018 at 10:30:51AM +0800, Jason Wang wrote:
> On 2018年05月19日 10:29, Tiwei Bie wrote:
> > > I don't hope so.
> > >
> > > > I agreed driver should track the DMA addrs or some
> > > > other necessary things from the very beginning. And
> > > > I also repeated the spec to emphasize that it does
> > > > make sense. And I'd like to do that.
> > > >
> > > > What I was saying is that, to support OOO, we may
> > > > need to manage these context (which saves DMA addrs
> > > > etc) via a list which is similar to the desc list
> > > > maintained via `next` in split ring instead of an
> > > > array whose elements always can be indexed directly.
> > > My point is these context is a must (not only for OOO).
> > Yeah, and I have the exactly same point after you
> > pointed that I shouldn't get the addrs from descs.
> > I do think it makes sense. I'll do it in the next
> > version. I don't have any doubt about it. All my
> > questions are about the OOO, instead of whether we
> > should save context or not. It just seems that you
> > thought I don't want to do it, and were trying to
> > convince me that I should do it.
>
> Right, but looks like I was wrong :)
>
> >
> > > > The desc ring in split ring is an array, but its
> > > > free entries are managed as list via next. I was
> > > > just wondering, do we want to manage such a list
> > > > because of OOO. It's just a very simple question
> > > > that I want to hear your opinion... (It doesn't
> > > > means anything, e.g. It doesn't mean I don't want
> > > > to support OOO. It's just a simple question...)
> > > So the question is yes. But I admit I don't have better idea other than what
> > > you propose here (something like split ring which is a little bit sad).
> > > Maybe Michael had.
> > Yeah, that's why I asked this question. It will
> > make the packed ring a bit similar to split ring
> > at least in the driver part. So I want to draw
> > your attention on this to make sure that we're
> > on the same page.
>
> Yes. I think we are.
Cool. Glad to hear that! Thanks! :)
Best regards,
Tiwei Bie
>
> Thanks
>
> > Best regards,
> > Tiwei Bie
> >
>
next prev parent reply other threads:[~2018-05-21 2:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 8:37 [RFC v4 0/5] virtio: support packed ring Tiwei Bie
2018-05-16 8:37 ` [RFC v4 1/5] virtio: add packed ring definitions Tiwei Bie
2018-05-16 8:37 ` [RFC v4 2/5] virtio_ring: support creating packed ring Tiwei Bie
2018-05-16 8:37 ` [RFC v4 3/5] virtio_ring: add packed ring support Tiwei Bie
2018-05-16 11:50 ` Jason Wang
2018-05-16 12:39 ` Tiwei Bie
2018-05-16 12:51 ` Jason Wang
2018-05-16 13:45 ` Tiwei Bie
2018-05-16 14:05 ` Jason Wang
2018-05-16 14:33 ` Tiwei Bie
2018-05-17 12:01 ` Jason Wang
2018-05-18 11:29 ` Tiwei Bie
2018-05-18 13:17 ` Jason Wang
2018-05-18 14:33 ` Tiwei Bie
2018-05-19 1:12 ` Jason Wang
2018-05-19 2:29 ` Tiwei Bie
2018-05-21 2:30 ` Jason Wang
2018-05-21 2:39 ` Tiwei Bie [this message]
2018-05-16 8:37 ` [RFC v4 4/5] virtio_ring: add event idx support in packed ring Tiwei Bie
2018-05-16 12:17 ` Jason Wang
2018-05-16 12:58 ` Tiwei Bie
2018-05-16 13:31 ` Jason Wang
2018-05-16 8:37 ` [RFC v4 5/5] virtio_ring: enable " Tiwei Bie
2018-05-16 10:15 ` Sergei Shtylyov
2018-05-16 10:21 ` Tiwei Bie
2018-05-16 11:42 ` Sergei Shtylyov
2018-05-16 12:26 ` Tiwei Bie
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=20180521023944.GA16702@debian \
--to=tiwei.bie@intel.com \
--cc=jasowang@redhat.com \
--cc=jfreimann@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=wexu@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).