From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) by dpdk.org (Postfix) with ESMTP id D6E982B97 for ; Wed, 23 Mar 2016 16:34:11 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2776; q=dns/txt; s=iport; t=1458747252; x=1459956852; h=from:to:cc:subject:date:message-id:mime-version; bh=N7bZyO27xTAHjBteEFMXWknd1mYEdg8ume99B1cm02U=; b=FnKpKGvq50Yn94EkSj6QCo18uiTYqOGa59mpQ/rdm0NLpSCFs8g4kTut euPc34X0u+mboGITqUuUBM82Q/e0+91QZGzSM3+GCgFy9jyGjIk9yXk5c vlWdef1k1/Aknd5khzj+fhJ868lGISv97IejrZl2IiUVPplrElwz6ZJlo M=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AdAgBPtvJW/5xdJa1egmdMgVO1cIJfg?= =?us-ascii?q?g8BDYFwhg2BPjgUAQEBAQEBAWQcC4REBHkSAQx0JwQOiCzBCQEBAQEBAQQBAQE?= =?us-ascii?q?BAQEBARiUdAWXWgGOA48KjwYBHgEBQoNliXd+AQEB?= X-IronPort-AV: E=Sophos;i="5.24,382,1454976000"; d="scan'208,217";a="252833432" Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Mar 2016 15:34:10 +0000 Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id u2NFYAo7023201 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 23 Mar 2016 15:34:10 GMT Received: from xch-rcd-004.cisco.com (173.37.102.14) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Wed, 23 Mar 2016 10:34:10 -0500 Received: from xch-rcd-004.cisco.com ([173.37.102.14]) by XCH-RCD-004.cisco.com ([173.37.102.14]) with mapi id 15.00.1104.009; Wed, 23 Mar 2016 10:34:10 -0500 From: "shesha Sreenivasamurthy (shesha)" To: "dev@dpdk.org" CC: "yuanhan.liu@linux.intel.com" Thread-Topic: DPDK's vhost-user logging capability Thread-Index: AQHRhRlx0cmYXMBiZUW/EIm74DmScw== Date: Wed, 23 Mar 2016 15:34:09 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.24.50.78] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-dev] DPDK's vhost-user logging capability X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Mar 2016 15:34:12 -0000 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 impl= emented 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; }