From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wr0-f179.google.com (mail-wr0-f179.google.com [209.85.128.179]) by dpdk.org (Postfix) with ESMTP id 00B5A378B for ; Fri, 9 Jun 2017 22:17:42 +0200 (CEST) Received: by mail-wr0-f179.google.com with SMTP id q97so43883508wrb.2 for ; Fri, 09 Jun 2017 13:17:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:references:to:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=2Fs5HtkjP+gqE35tleYh2leRs5uLZeTqcX+GEYbTiqE=; b=Ed2UPBmCdlQQZ0Ro8Ou79pXbAGRHTdtJj1qwXBCFhTcoCkafwHyXl0ugaVrC7wF2aS ahNoENNRYqDnTijL+uHwFK2FhPDOQBIAHFH9kVBw33CcjdRUMviBvvD/gNCtkb9K7m6Q fAtPahK35W5J1PrtT9DW2wYFqPc1AUmaQTh1Wyf5BRyBYg3gPRpgHiO4HtbZPsAIgf2t nnIW6KBYFbrpRUDVHEx9Ax67YJiBOKCLQJrdoIkfDZHKFseNYcT38jOpLurh92aLk+v8 qtJK162KSHljyb4dhOoPoiR+H4F4vG1T7H6irn+Sns4w1Rd4XwAKlZceK7pMjQEgz+Jg 3eEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:references:to:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=2Fs5HtkjP+gqE35tleYh2leRs5uLZeTqcX+GEYbTiqE=; b=MiDJOqwgHs/maJE8yMXFil9phtg0+yN2vNYGMZ6APY2WXqZ+vMHVe7PJH28fRlVh1C Y1Fa4VPMV4xiOAD1xR3oo/524oT/whWTGdvrwst83zTM2ATRQ/6ODrn07bU69Fh82hyv hcVB1cgEkxfHViYOnvC6HQRCjvObvehaXuIdUca8RQIhhlrYfa1F89GopYSZ0h6zpc1L 8kju3nM5iNv7GE1AwiSkzl5yKnBZAOL2SIUVDAW2Tr67uqcrQHccCbbKK/zEexz3MJII 0hoviAp35EUh6g/zKJaHyhL97mAXCTb58b9oVIafvJyzD2ZJ+Q8GnkbBoWN8HhwSbOjP s8cw== X-Gm-Message-State: AKS2vOzTBJFCG/lCzE6V6sdejS/BBOGcc3Ll+1c9O2Sf5T4XLkQflkpV vQxx7lcpQbG906sCNsk= X-Received: by 10.28.199.75 with SMTP id x72mr1106823wmf.17.1497039462474; Fri, 09 Jun 2017 13:17:42 -0700 (PDT) Received: from [192.168.2.222] (LFbn-1-12755-177.w90-90.abo.wanadoo.fr. [90.90.58.177]) by smtp.gmail.com with ESMTPSA id w128sm737616wmd.7.2017.06.09.13.17.41 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Jun 2017 13:17:41 -0700 (PDT) References: To: users@dpdk.org From: Jean-Philippe ANDRIOT X-Forwarded-Message-Id: Message-ID: <12e40f2e-6bd3-1443-9895-0dd75e82a769@gmail.com> Date: Fri, 9 Jun 2017 22:17:40 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Language: en-US Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] Is it possible to use distributor library in multi-process mode ? X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jun 2017 20:17:43 -0000 Hi, I would like to use packet distributor library in multi-process mode, meaning both distributor core and every worker are running in a different process (secondary proc type). However, there is no /rte_distributor_lookup/ function to get a distributor instance from a DPDK secondary process, such as /rte_ring_lookup/ for rings. I had a look to the implementation of both ring and distributor and it looks like both are created the same way (rte_memzone allocation and registration in a RTE_TAILQ in shm). So I'm wondering if the rte_distributor_lookup function could be easily implemented ( based on rte_ring_lookup ) or if there are specific issues which prevent distributor to be used in multi process mode. Thanks !