From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vk0-f52.google.com (mail-vk0-f52.google.com [209.85.213.52]) by dpdk.org (Postfix) with ESMTP id 476044AC7 for ; Fri, 15 Apr 2016 23:57:57 +0200 (CEST) Received: by mail-vk0-f52.google.com with SMTP id e185so162785127vkb.1 for ; Fri, 15 Apr 2016 14:57:57 -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=dlek5YEgQ2d3WGBL52DmjxLHDW1SoFwMLc2i97C3jQo=; b=En7NYS6u/4BlW3UubEQfCFEi8OIRBjsOEfm0aQhdYn1JLYLMoyleqHSpJOHflzsVFb sSmNhXwOhrwzXN8J5t3JTU8+hgcM3QVC7fiwCsBoA8ZIs2cEeAvxtNcBREB49aSKFT/w R39zFsUR3pEPQTs7rwnNbDz4nn4Bc9VoUcYh0lI8OMsMml6GJzh7bq3UCvx8u2G4RsQL hREYLv5yUp0P6k5A42bPjKuhdz+AdduVS52v7a+j9HhnBK26NM26KMkgWWRPTwhlSDvd vZyy6EvDO6/tVmDzvPo8J+ckCx8WJsF4e/dI/VvD/9EgKgXpS679YpwqgvJ85YFLPbCv lTDA== 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=dlek5YEgQ2d3WGBL52DmjxLHDW1SoFwMLc2i97C3jQo=; b=EjHfoA7inqYzT5p9WK3LpH6Hgzv1V+xm1Oxv8pI1fuLaC+eqPuPUfBrnA6P1Ca+ReF UVIRdTwYZh04aoJoqydR4ipcB58Og0AFmc0vmzwFqDL0PNJUDVnuV+t+NbtH9q9+xhLB csb0NYXXx61MSSoVmvRUkVH7am2vYDGe5VCFIIOmHW4NszNaKkvWO8APrclM8qrVu7Uf ba91gfbTF7l9TfT3jpXynm1y2fXxxt2+2maERNXfl7gp8oQ05i1nB1YLqK+fqR52k554 VNNTISDUj6xVhshCaLDn/3uwPkuLG7pNgll0qKAElhDX/dNqzVHK1ik4ulHFg52X7eAS 6c/w== X-Gm-Message-State: AOPr4FXcsgoRZpgs+QuVzrKbpwIAi/ZXqkPDi0rJ8qabKZP9cOstqUy39+LNt69tOGWwlLUi+fZac3gR6Uk6Ag== MIME-Version: 1.0 X-Received: by 10.31.136.65 with SMTP id k62mr11659005vkd.145.1460757476681; Fri, 15 Apr 2016 14:57:56 -0700 (PDT) Received: by 10.176.5.194 with HTTP; Fri, 15 Apr 2016 14:57:56 -0700 (PDT) In-Reply-To: <20160413111013.2d56cb28@xeon-e3> References: <20160413111013.2d56cb28@xeon-e3> Date: Fri, 15 Apr 2016 14:57:56 -0700 Message-ID: From: Cliff Burdick To: Stephen Hemminger Cc: users Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] Coremask 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, 15 Apr 2016 21:57:57 -0000 Thanks Stephen. One of the issues I'm having is that it seems the master lcore is the *only* one that can receive from one of the queues I created on a port. For instance, I start my app with 5 cores, 0-4, where I want 1-4 to listen to port 0 , queue 0-3, and core 0 to be the master. I launch all 4 workers with rte_eal_remote_launch on cores 1-4, and the master (0) sits there waiting on rte_eal_mp_wait_lcore(). However, I receive no packets on core 1 even though it's listening to the proper queue. If I copy the code that's listening on core 1 and stick it in the master lcore, it sees all the packets. Is there some lcore->queue binding that I'm missing? I thought that by launching with rte_eal_remote_launch on all but the master core would work, but it doesn't. My main goal is to have the master run on its own core not doing packet processing, but periodically printing stats out. It's similar to the l2fwd example, except in that example, the master is also processing packets. On Wed, Apr 13, 2016 at 11:10 AM, Stephen Hemminger < stephen@networkplumber.org> wrote: > On Wed, 13 Apr 2016 09:42:29 -0700 > Cliff Burdick wrote: > > > I don't see the answer to this in the documentation, so I'll try here. > Why > > function does the coremask that's required in rte_eal_init() actually do > > other than tell the API what cores you're using? In other words, can't I > > just set the core mask to all of the cores in my system, and selectively > > use the ones I want? Is there a downside to that? What if the particular > > thread running on an lcore isn't doing any DPDK functions? > > The coremask is used to determine which CPU's are setup and a per-cpu > thread is started by the launch operation. > > You can tell EAL about as many CPU's as you want, either all or even > just one. If you use all CPU's, then in the launch it is possible to > have the thread function of unneeded CPU's return and go back to the > launch idle loop. >