From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-f180.google.com (mail-wi0-f180.google.com [209.85.212.180]) by dpdk.org (Postfix) with ESMTP id 174FB9AD8 for ; Tue, 24 Feb 2015 19:53:38 +0100 (CET) Received: by mail-wi0-f180.google.com with SMTP id h11so27482279wiw.1 for ; Tue, 24 Feb 2015 10:53:37 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=37NO6vNeAbAflDolgt4ENR3LuymiryjQILARIAhPqZg=; b=Sdgy39Ex2LpZ2evKCNIYpTmAch4WNAAty1LQDMRYAal+tkdsinPAiCb0M02/6ImfZz k3CpNoARuF2VdmYGVqmzKGlu7F1uG7+yFKNuVBDyuBTYoRrEg6IRrfQAcRkaeyPsG2Wx PF53bfMaVc+zEeYfokIl3uG6+/IoTdJ5AmEH3z1pe8Cg6pdsl3lbSQFuZDswR7v/SCDk clmgW6JBHUaEOdyUmfLOf6IqAOqN3hTL6YGVVuNOCVRrqVV0tx45DE4cCGDQ4bD5hF8H XcHdfbkfTCdaFDUaokUGBz5nn9nOYf/ausG9VwlcyWNRqcHPeUxAGvoRzazbH0b4rgGE exBw== X-Gm-Message-State: ALoCoQm9+s8y0T3UEnHtIzxqIC2YQ0tB/84WlX8R2D/WHosAV6ej4fkLmdH5rXmxwbe19fPt/X9Y X-Received: by 10.180.126.98 with SMTP id mx2mr32707910wib.18.1424804017839; Tue, 24 Feb 2015 10:53:37 -0800 (PST) Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136]) by mx.google.com with ESMTPSA id b4sm3990266wic.2.2015.02.24.10.53.34 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 24 Feb 2015 10:53:35 -0800 (PST) From: Thomas Monjalon To: "Liang, Cunming" Date: Tue, 24 Feb 2015 19:53:03 +0100 Message-ID: <2206208.RNY87Zy52I@xps13> Organization: 6WIND User-Agent: KMail/4.14.4 (Linux/3.18.4-1-ARCH; KDE/4.14.4; x86_64; ; ) In-Reply-To: <2601191342CEEE43887BDE71AB977258213EE0A9@irsmsx105.ger.corp.intel.com> References: <1423970145-31985-1-git-send-email-cunming.liang@intel.com> <1424138896-28618-1-git-send-email-cunming.liang@intel.com> <2601191342CEEE43887BDE71AB977258213EE0A9@irsmsx105.ger.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH v8 00/19] 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: Tue, 24 Feb 2015 18:53:38 -0000 > > v8 changes: > > keep using strlen for trusted input string > > > > v7 changes: > > update EAL version map for new public EAL API > > rollback to use strnlen() passing EAL core option > > > > v6 changes: > > rename RTE_RING_PAUSE_REP(_COUNT) and set default to 0 > > rollback to use RTE_MAX_LCORE when checking valid lcore_id for EAL thread > > > > v5 changes: > > reorder some patch and split into addtional two patches > > rte_thread_get_affinity() return type change to avoid > > add RTE_RING_PAUSE_REP into config and by default turn off > > > > 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. > > > > Thanks a million for the comments from Konstantin, Bruce, Mirek and Stephen in RFC review. > > > > Cunming Liang (19): > > eal: add cpuset into per EAL thread lcore_config > > eal: fix PAGE_SIZE redefine complaint on freebsd > > eal: new eal option '--lcores' for cpu assignment > > eal: fix wrong strnlen() return value in 32bit icc > > eal: add public function parsing socket_id from cpu_id > > eal: new TLS definition and API declaration > > eal: add eal_common_thread.c for common thread API > > eal: standardize init sequence between linux and bsd > > eal: add rte_gettid() to acquire unique system tid > > eal: apply affinity of EAL thread by assigned cpuset > > enic: fix re-define freebsd compile complain > > malloc: fix the issue of SOCKET_ID_ANY > > log: fix the gap to support non-EAL thread > > eal: set _lcore_id and _socket_id to (-1) by default > > eal: fix recursive spinlock in non-EAL thraed > > mempool: add support to non-EAL thread > > ring: add support to non-EAL thread > > ring: add sched_yield to avoid spin forever > > timer: add support to non-EAL thread > > Acked-by: Konstantin Ananyev I tried to fix many english typos. Please consider it during reviews. Cunming, you'll repeat 10 times "non-EAL threads compute more than none" ;) Applied, thanks My main concern in this patchset is about naming. Now lcore means thread in many places. I would prefer to have a cleanup to use right term at right place, even if it requires breaking API. Are we going to deprecate the fresh option -l in favor of --lcores/--threads?