From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw0-f193.google.com (mail-yw0-f193.google.com [209.85.161.193]) by dpdk.org (Postfix) with ESMTP id EBC8A298F for ; Thu, 24 Mar 2016 08:16:31 +0100 (CET) Received: by mail-yw0-f193.google.com with SMTP id o63so632241ywe.0 for ; Thu, 24 Mar 2016 00:16:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=pPlgvvSxtRCKZpk+9iArP9tEt9OM9QzbXVWlfqjAD+4=; b=1Is+d2Ott0SCrupEnZDhfYEhuq68EmkdUAFw/RbcYfmgLoE4wR64GeZvtrYTTyiex6 UI9q3mQdJ/T590AuynItOkdbrp1XfrR/37hyMXlX6huCpZZQ+DSMF5S1Jg3zpe4AIPIU fFzyd+5cBbmVS4+s0p5Xh+USse5z1Y1xd1QBJSuS/5X6pynA9iR9OXav3eH7t13YgTJ0 3lXne/c693oiZrq1hSvpgJewn2AynhqYKmTRGMALXF32vHkZ9toBDXc7hz5J5ADlI6l8 eXtd+o60fIYguFDTJUCtYSgYgE/6U/q27Hh7z9lJxon/lFNmdg2E9WRh/is3rp22Tpl6 swow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=pPlgvvSxtRCKZpk+9iArP9tEt9OM9QzbXVWlfqjAD+4=; b=TicmU9AEIyFZdWatMpNQBXS2QAaEmS1bKq8w/BbU07U+QqdC+aZ0YgHPnBLakpu1LG V2n/gKEGVoKQGQTQ7XcVn0P7K+O8eabysT35JVbQJ+Lp6XfyAwWtmQtnYUyXGqZTzpqT 7FhiJyPka31H556NLu7TxAqaSrYtJbCRuvnq9r9VVDTTh5k7MbHNfyffs03Z/Dq2HRBn fGBrcLQR/R25mtLrtL/Hd7K9AM7T8YpNSRakfQKFuAyOOc0cCZmoMn2z6NZmaAcMZ9/i l9Q4bF0KJDfP1wBkHLOugnsP2EJ3yqnEvqwUn/TLkja2uSPWZp355vfd+bwALrJC2S12 ZPPA== X-Gm-Message-State: AD7BkJJ87Th1uRO98UgbOq77B2DCOP7JNkmPuC8X0xhpjSZ1d5pGqWuGMbxWCF0vDcNCBA== X-Received: by 10.129.156.142 with SMTP id t136mr3371937ywg.152.1458803791361; Thu, 24 Mar 2016 00:16:31 -0700 (PDT) Received: from mail-yw0-f178.google.com (mail-yw0-f178.google.com. [209.85.161.178]) by smtp.gmail.com with ESMTPSA id c67sm3791591ywb.41.2016.03.24.00.16.29 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 Mar 2016 00:16:29 -0700 (PDT) Received: by mail-yw0-f178.google.com with SMTP id h65so48758458ywe.0 for ; Thu, 24 Mar 2016 00:16:29 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.129.120.74 with SMTP id t71mr3430564ywc.142.1458803789487; Thu, 24 Mar 2016 00:16:29 -0700 (PDT) Received: by 10.37.35.86 with HTTP; Thu, 24 Mar 2016 00:16:29 -0700 (PDT) In-Reply-To: <54CBAA185211B4429112C315DA58FF6DDDA481@IRSMSX103.ger.corp.intel.com> References: <54CBAA185211B4429112C315DA58FF6DDDA481@IRSMSX103.ger.corp.intel.com> Date: Thu, 24 Mar 2016 15:16:29 +0800 X-Gmail-Original-Message-ID: Message-ID: From: Royce Niu To: "Singh, Jasvinder" Cc: Royce Niu , "users@dpdk.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] Why we need [MASTER] in DPDK Pipeline 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: Thu, 24 Mar 2016 07:16:32 -0000 Thanks! Your explanation is quite clear. But, we I assign one core to VM and use this one core to start the pipeline. It shows : sudo ./build/ip_pipeline -f l2fwd.cfg -p 0x6 [APP] Initializing CPU core map ... PANIC in app_init_core_map(): Cannot create CPU core map 6: [./build/ip_pipeline() [0x431b43]] 5: [/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7efdd5090ec5]] 4: [./build/ip_pipeline(main+0x5f) [0x4306ff]] 3: [./build/ip_pipeline(app_init+0x14fb) [0x43f7ab]] 2: [./build/ip_pipeline(__rte_panic+0xc9) [0x42b11a]] 1: [./build/ip_pipeline(rte_dump_stack+0x1a) [0x4c9fba]] The config is : [PIPELINE0] type = MASTER core = 0 [PIPELINE1] type = PASS-THROUGH core = 0 pktq_in = RXQ0.0 RXQ1.0 pktq_out = TXQ1.0 TXQ0.0 The VM start cmd is : sudo taskset 0x10 ./qemu-system-x86_64* -enable-kvm -cpu host -m 1024M -smp sockets=1,cores=1* -netdev tap,id=hostnet0 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:5e:cc:f0 /trunk/template.img -chardev socket,id=char0,path=/tmp/sn_vhost_vh0 -netdev type=vhost-user,id=mynet0,chardev=char0,vhostforce -device virtio-net-pci,netdev=mynet0,mac=52:54:00:02:d9:00 -chardev socket,id=char1,path=/tmp/sn_vhost_vh1 -netdev type=vhost-user,id=mynet1,chardev=char1,vhostforce -device virtio-net-pci,netdev=mynet1,mac=52:54:00:02:d9:01 -object memory-backend-file,id=mem,size=1024M,mem-path=/dev/hugepages,share=on -numa node,memdev=mem -mem-prealloc -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 However, when I assign two vCPUs to the VM and assign P0 and P1 in different vCPU. Everything is right. On Thu, Mar 24, 2016 at 4:06 AM, Singh, Jasvinder wrote: > Hi Royce, > > > -----Original Message----- > > From: users [mailto:users-bounces@dpdk.org] On Behalf Of Royce Niu > > Sent: Wednesday, March 23, 2016 3:51 PM > > To: users@dpdk.org > > Subject: [dpdk-users] Why we need [MASTER] in DPDK Pipeline > > > > Dear all, > > > > I am using DPDK Pipeline to build a Firewall. I found assign a core to > MASTER. > > Could you please tell me why we need MASTER? and why MASTER need a > > dedicated core ? since I meet error to bind MASTER and Firewall to same > > core. > > > > Master pipeline, basically is a management thread that allow users to > interact and manage ip-pipeline application during run time. It offers CLI > to configure ports, collecting stats, add/remove table entries, loading > rules files, displaying rules, quit etc. Therefore, the master pipeline > receives inputs from the user, translates them into formal command and > forwards command to the desired pipeline (data plane thread). The packet > processing pipeline which is continuously working on the packets > periodically checks whether there is any command to handle or not, and > execute them accordingly if there is any. In addition to this, master > pipeline also maintains a copy of all the tables used in pipelines. If user > wants to inspect the rules, master pipeline will display them without > interrupting data plane thread. > > Now, if anyone don't want to assign dedicated core to master pipeline, > then it should also work. However, a slight impact on the performance may > be visible depending the commands being run. > > In your case, you can bind both master and firewall pipelines to single > core and they should work correctly. > > Thanks. > > Regards, > Jasvinder > -- Regards, Royce Niu