From: "Marc-André Lureau" <mlureau@redhat.com>
To: Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: "shesha Sreenivasamurthy (shesha)" <shesha@cisco.com>,
dev@dpdk.org, "Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: Re: DPDK's vhost-user logging capability
Date: Fri, 25 Mar 2016 07:08:52 -0400 (EDT) [thread overview]
Message-ID: <609417283.14385576.1458904132070.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20160325024959.GZ979@yliu-dev.sh.intel.com>
Hi
----- Original Message -----
> On Wed, Mar 23, 2016 at 03:34:09PM +0000, shesha Sreenivasamurthy (shesha)
> wrote:
> > Hi All,
> >
> > I was going over vhost-user migration capability in DPDK in lieu of a
> > Cisco's
> > multi-q DPDK vhost-user application. I see that log_base address is
> > implemented
> > as per virtio_net device. However, desc, addr and used is per
> > vhost_virtqueue.
> > Additionally, QEMU sends one VHOST_USER_SET_LOG_BASE per queue-pair (QEMU -
> > hw/
> > virtio/vhost.c::vhost_dev_set_log).
> >
> > Does it mean we need to log dirty pages of all rings to same location ?
>
> Hi,
>
> Yes, and QEMU allocates only one block of memory (see vhost_log_alloc())
> after all.
> > If that
> > is the case then why does QEMU sends separate VHOST_USER_SET_LOG_BASE per
> > queue
> > pair ?
>
> That's kind of like a design. One queue pair is associated with one
> vhost_dev struct in QEMU, hence, all those requests will go through
> vhost_dev structs (aka, all qeueu pairs), including those that one
> time request is needed only, such as VHOST_USER_SET_MEM_TABLE. Thus,
> we introduced vhost_user_one_time_request() to avoid such case.
I am not familiar with multi-queue, but I can see that in vhost_net_start.
> So, good question, and we may need add it to the "one time request"
> group, Marc?
That would probably prevent vhost_dev_log_resize(), so it would need some kind of "force" flag. I am not sure it's worth it at this point.
>
> And FYI, for queue-pair (or vring) request, there should be an index
> in the payload, to point to the right vring. If not, it normally
> means a global request, that _may_ need be sent once only.
>
> --yliu
>
prev parent reply other threads:[~2016-03-25 11:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 15:34 DPDK's vhost-user logging capability shesha Sreenivasamurthy (shesha)
2016-03-25 2:49 ` Yuanhan Liu
2016-03-25 11:08 ` Marc-André Lureau [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=609417283.14385576.1458904132070.JavaMail.zimbra@redhat.com \
--to=mlureau@redhat.com \
--cc=dev@dpdk.org \
--cc=marcandre.lureau@redhat.com \
--cc=shesha@cisco.com \
--cc=yuanhan.liu@linux.intel.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 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.