From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from serv108.segi.ulg.ac.be (serv108.segi.ulg.ac.be [139.165.32.111]) by dpdk.org (Postfix) with ESMTP id 55E86567F for ; Fri, 27 Nov 2015 12:20:31 +0100 (CET) Received: from mbx12-zne.ulg.ac.be (serv470.segi.ulg.ac.be [139.165.32.199]) by serv108.segi.ulg.ac.be (Postfix) with ESMTP id 260C620179D4 for ; Fri, 27 Nov 2015 12:20:31 +0100 (CET) Received: from localhost (localhost.localdomain [127.0.0.1]) by mbx12-zne.ulg.ac.be (Postfix) with ESMTP id 1FC50129E886 for ; Fri, 27 Nov 2015 12:20:31 +0100 (CET) Received: from mbx12-zne.ulg.ac.be ([127.0.0.1]) by localhost (mbx12-zne.ulg.ac.be [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id SS-1tCzkLYAr for ; Fri, 27 Nov 2015 12:20:31 +0100 (CET) Received: from mbx12-zne.ulg.ac.be (mbx12-zne.ulg.ac.be [139.165.32.199]) by mbx12-zne.ulg.ac.be (Postfix) with ESMTP id EF231129E884 for ; Fri, 27 Nov 2015 12:20:30 +0100 (CET) Date: Fri, 27 Nov 2015 12:20:30 +0100 (CET) From: tom.barbette@ulg.ac.be To: users@dpdk.org Message-ID: <1776090861.33566100.1448623230858.JavaMail.zimbra@ulg.ac.be> In-Reply-To: <1773807014.33559428.1448622341610.JavaMail.zimbra@ulg.ac.be> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [139.165.223.24] X-Mailer: Zimbra 8.0.9_GA_6191 (ZimbraWebClient - GC46 (Linux)/8.0.9_GA_6191) Thread-Topic: Multiple (uncooperative) DPDK process Thread-Index: +CRbMdxD7iP8RpG5UeRjdnQk11DuGw== Subject: [dpdk-users] Multiple (uncooperative) DPDK process X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Nov 2015 11:20:31 -0000 Hi all, I'd like to run multiple DPDK application on the same host, without virtualization (no QEMU/KVM). A "dispatcher" application will run as a primary process and send packets to multiple other application running as secondary process (NFV applications). I found out that DPDK Rings are probably my best choice for that (do you agree by the way?) For the example, let the "dispatcher" application be OVS-DPDK, which will be the primary process, it will allocate a mempool with some random name (->no standard way to define it). I'll create a ring in OVS, and I'd like my NFV applications to connect to those rings. But they don't know the name of the mempool, as my application are independent. Moreover, OVS is just an example and other applications I'd like to use could even not specify a name (with OVS, we can at least recover the name, but it's not very "clean"). Is there a clean solution for that problem? Should OVS-DPDK allow to pass a mempool name in argument? Or should I use rte_mempool_walk and attach myself to the first mempool I get? Thanks ! Tom