From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.droids-corp.org (zoll.droids-corp.org [94.23.50.67]) by dpdk.org (Postfix) with ESMTP id 682D7234 for ; Fri, 6 Feb 2015 16:47:54 +0100 (CET) Received: from was59-1-82-226-113-214.fbx.proxad.net ([82.226.113.214] helo=[192.168.0.10]) by mail.droids-corp.org with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from ) id 1YJlBv-0003af-SJ; Fri, 06 Feb 2015 16:51:40 +0100 Message-ID: <54D4E21F.6000401@6wind.com> Date: Fri, 06 Feb 2015 16:47:43 +0100 From: Olivier MATZ User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.3.0 MIME-Version: 1.0 To: Cunming Liang , dev@dpdk.org References: <1422491072-5114-1-git-send-email-cunming.liang@intel.com> <1422842559-13617-1-git-send-email-cunming.liang@intel.com> In-Reply-To: <1422842559-13617-1-git-send-email-cunming.liang@intel.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v4 00/17] support multi-pthread per core 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: Fri, 06 Feb 2015 15:47:54 -0000 Hi, On 02/02/2015 03:02 AM, Cunming Liang wrote: > v4 changes: > new patch fixing strnlen() invalid return in 32bit icc [03/17] > update and add more comments on sched_yield() [16/17] > > v3 changes: > new patch adding sched_yield() in rte_ring to avoid long spin [16/17] > > v2 changes: > add '-' support for EAL option '--lcores' [02/17] > > The patch series contain the enhancements of EAL and fixes for libraries > to run multi-pthreads(either EAL or non-EAL thread) per physical core. > Two major changes list as below: > - Extend the core affinity of each EAL thread to 1:n. > Each lcore stands for a EAL thread rather than a logical core. > The change adds new EAL option to allow static lcore to cpuset assginment. > Then a lcore(EAL thread) affinity to a cpuset, original 1:1 mapping is the special case. > - Fix the libraries to allow running on any non-EAL thread. > It fix the gaps running libraries in non-EAL thread(dynamic created by user). > Each fix libraries take care the case of rte_lcore_id() >= RTE_MAX_LCORE. Sorry if I missed something, but after reading the mailing list threads about this subject, I cannot find an explanation about what problem this series try to solve. Can you give some details about which use-case require to have multiple pthreads per cpu? What are the advantage of doing so? Regards, Olivier