From: Shirley Ma <mashirle@us.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: David Miller <davem@davemloft.net>,
netdev@vger.kernel.org, jasowang@redhat.com
Subject: Re: [PATCH] vhost: clean up outstanding buffers before setting vring
Date: Tue, 19 Jul 2011 13:50:53 -0700 [thread overview]
Message-ID: <1311108653.8573.25.camel@localhost.localdomain> (raw)
In-Reply-To: <20110719194956.GC8667@redhat.com>
On Tue, 2011-07-19 at 22:49 +0300, Michael S. Tsirkin wrote:
> On Tue, Jul 19, 2011 at 11:02:26AM -0700, Shirley Ma wrote:
> > The outstanding DMA buffers need to be clean up before setting vring
> in
> > vhost. Otherwise the vring would be out of sync.
> >
> > Signed-off-by: Shirley Ma<xma@us.ibm.com>
>
> I suspect what is missing is calling
> vhost_zerocopy_signal_used then?
>
> If yes we probably should do it after
> changing the backend, not on vring set.
I think vhost_zerocopy_signal_used might not be sufficient. But we can
test it out by remove/reloading the guest virtio_net module.
> > ---
> >
> > drivers/vhost/vhost.c | 11 +++++++++--
> > 1 files changed, 9 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/vhost/vhost.c b/drivers/vhost/vhost.c
> > index c14c42b..d6315b4 100644
> > --- a/drivers/vhost/vhost.c
> > +++ b/drivers/vhost/vhost.c
> > @@ -445,8 +445,10 @@ void vhost_dev_cleanup(struct vhost_dev *dev)
> > vhost_poll_flush(&dev->vqs[i].poll);
> > }
> > /* Wait for all lower device DMAs done. */
> > - if (dev->vqs[i].ubufs)
> > + if (dev->vqs[i].ubufs) {
> > vhost_ubuf_put_and_wait(dev->vqs[i].ubufs);
> > + kfree(dev->vqs[i].ubufs);
> > + }
> >
> > /* Signal guest as appropriate. */
> > vhost_zerocopy_signal_used(&dev->vqs[i]);
> > @@ -651,6 +653,12 @@ static long vhost_set_vring(struct vhost_dev
> *d, int ioctl, void __user *argp)
> > vq = d->vqs + idx;
> >
> > mutex_lock(&vq->mutex);
> > + /* Wait for all lower device DMAs done. */
> > + if (vq->ubufs)
> > + vhost_ubuf_put_and_wait(vq->ubufs);
>
> Could you elaborate on the problem you observe please?
> At least in theory, existing code flushes outstanding
> requests when backend is changed.
> And since vring set verifies no backend is active,
> we should be fine?
The problem encounters when guest rmmod virtio_net module, then reload
the module, and configure the interface, it complains about some ring id
is not a head. With this patch, the problem is solved.
>
> > +
> > + /* Signal guest as appropriate. */
> > + vhost_zerocopy_signal_used(vq);
> >
> > switch (ioctl) {
> > case VHOST_SET_VRING_NUM:
> > @@ -1592,7 +1600,6 @@ void vhost_ubuf_put_and_wait(struct
> vhost_ubuf_ref *ubufs)
> > {
> > kref_put(&ubufs->kref, vhost_zerocopy_done_signal);
> > wait_event(ubufs->wait, !atomic_read(&ubufs->kref.refcount));
> > - kfree(ubufs);
>
> Won't this leak memory when ubufs are switched in
> vhost_net_set_backend?
Right, I forgot to check net.c, whenever it calls
vhot_ubuf_put_and_wait, it should call kfree(ubufs).
next prev parent reply other threads:[~2011-07-19 20:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-19 18:02 [PATCH] vhost: clean up outstanding buffers before setting vring Shirley Ma
2011-07-19 19:49 ` Michael S. Tsirkin
2011-07-19 20:50 ` Shirley Ma [this message]
2011-07-20 10:41 ` Michael S. Tsirkin
2011-07-20 18:12 ` Shirley Ma
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=1311108653.8573.25.camel@localhost.localdomain \
--to=mashirle@us.ibm.com \
--cc=davem@davemloft.net \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.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 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).