From: "shesha Sreenivasamurthy (shesha)" <shesha@cisco.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "yuanhan.liu@linux.intel.com" <yuanhan.liu@linux.intel.com>
Subject: [dpdk-dev] DPDK's vhost-user logging capability
Date: Wed, 23 Mar 2016 15:34:09 +0000 [thread overview]
Message-ID: <D318036F.32CB9%shesha@cisco.com> (raw)
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 ? If that is the case then why does QEMU sends separate VHOST_USER_SET_LOG_BASE per queue pair ?
--
- Thanks
char * (*shesha) (uint64_t cache, uint8_t F00D)
{ return 0x0000C0DE; }
next reply other threads:[~2016-03-23 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 15:34 shesha Sreenivasamurthy (shesha) [this message]
2016-03-25 2:49 ` Yuanhan Liu
2016-03-25 11:08 ` Marc-André Lureau
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=D318036F.32CB9%shesha@cisco.com \
--to=shesha@cisco.com \
--cc=dev@dpdk.org \
--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 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).