From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id B39342A5D for ; Mon, 25 Apr 2016 15:21:44 +0200 (CEST) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by fmsmga103.fm.intel.com with ESMTP; 25 Apr 2016 06:21:43 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,532,1455004800"; d="scan'208";a="91465831" Received: from irsmsx152.ger.corp.intel.com ([163.33.192.66]) by fmsmga004.fm.intel.com with ESMTP; 25 Apr 2016 06:21:43 -0700 Received: from irsmsx109.ger.corp.intel.com ([169.254.13.57]) by IRSMSX152.ger.corp.intel.com ([169.254.6.15]) with mapi id 14.03.0248.002; Mon, 25 Apr 2016 14:21:41 +0100 From: "Burakov, Anatoly" To: David Verbeiren , "dev@dpdk.org" Thread-Topic: [dpdk-dev] [RFC PATCH] ivshmem ring aliases Thread-Index: AQHRbu7v5goB8zXYqUyP76iQ0nLJ95+bDECQ Date: Mon, 25 Apr 2016 13:21:41 +0000 Message-ID: References: <1456310006-30296-1-git-send-email-david.verbeiren@gmail.com> In-Reply-To: <1456310006-30296-1-git-send-email-david.verbeiren@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_IC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMDRhYTU2YTEtNmFjMi00YTViLTk1ODEtOTRhNTg2ZGIzMmMxIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6ImhVc1ZYZ1Z1eFE5Z0ZudnVMc0diTXBlYnpPc1FJV2hpaXQralwvcnU5Qmg4PSJ9 x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [RFC PATCH] ivshmem ring aliases 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: Mon, 25 Apr 2016 13:21:45 -0000 > The goal of this parch is to allow VMs to use standard ring names regardl= ess > of the names given to the rings by host environment. It applies to > configurations using ivshmem. >=20 > With shared memory rings, all VMs share a single namespace for the rings. > However, a VM will typically expect to find its rings with a pre-determin= ed > name (e.g. p1_rx, p1_tx) regardless of how it's deployed, inserted in a > service chain, or of which other VMs are deployed alongside it. Hence, it= is > desirable to introduce a level of indirection where the host can set a ma= pping > from the actual ring names (e.g. dpdkr0_rx|tx with OVS) and the names tha= t > will be visible in the VM. This patch provides a simple implementation of= such > a mapping scheme. >=20 > Since the mapping must be VM specific, the aliases are inserted into the > IVSHMEM metadata area by the host and the guest side uses thoses aliases > when doing rte_ring_lookup(). >=20 > A new function, rte_ivshmem_add_ring_alias() is provided in > librte_ivshmem to populate alias entries in the host environment when > creating the per-VM metadata. Don't have any objections to this RFC, looks sensible to me as a concept. S= o, provided the tests are passing, Acked-by: Anatoly Burakov =20