From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53]) by dpdk.org (Postfix) with ESMTP id B911568D9 for ; Fri, 16 Sep 2016 16:04:08 +0200 (CEST) Received: by mail-wm0-f53.google.com with SMTP id k186so43584668wmd.0 for ; Fri, 16 Sep 2016 07:04:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=pcUcEvH0yqzUaVlSUwvkPRfWB2fJ84FeHErOuGqujCg=; b=AXG1oT9IRKjP57Zkc0vKB8M6H76ktvqILYHAog0bo/EML/2y6UG+RNV+W3XdnpI2Nw +B/coiNuUwL0uN7OicwW1wm2dP2k3uKr+6Wg7Vn21CmEOcWoZFBVkxXBF65C9Ix8NP7y g+eCXW5IVrajhFC5ojyvedBoutfiwGuKDT0BUuv/Ky4/ACnpqUP50Qo2m+qewa8zme2k a4h2e42SpNNMH2hRCkEHe8ekIJOCpQDOBiQdFXILk++AawkJ/L3TlPa3xyaFxVKJ3les p2KehzcfAzkhI8FN4Uj5pZdXc7hcuIFiBlALJM0qwCljpBDE9UNLU8E3J5xOHrHDG/F1 UY8A== 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:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=pcUcEvH0yqzUaVlSUwvkPRfWB2fJ84FeHErOuGqujCg=; b=HxTssmM9aNSrINTw1CbYaJvVsTC0Qu2w4c6DUv60z4pip2YRn6TX1IricxScczT+H9 8kHAmSN5Dopk4S6S8hvoREO97z8OAkEp7hWpJiJo7M+wCg4/W7NhVtTegos9gRzv8pfX ini/UAwD/SyzzizNeE4epKOJw455VOk+PeGwn3L3/8B9j9hWWsK2vPVXwgwXZMYAIKJp Y9yXeVYfYoI3amEl4A2s4oRrZo5nPfy9ccM0zOtM5OHfozLuUqdAXTl1D75ufJOqnW96 gDTyvRG6rso00gztWRPpYVN91bv/gpzIAs0wHxXDVHPj20NL5NCy2wdhK8gZ0ZF4bQix cx4g== X-Gm-Message-State: AE9vXwO32ngoQ71yCnLpkIt/xbVL+VwO8B518ZbfxB040BYLX5L4QV9VBu3Z3jXq+DG5asF/ X-Received: by 10.28.91.11 with SMTP id p11mr7972780wmb.98.1474034648250; Fri, 16 Sep 2016 07:04:08 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id bw9sm8572928wjc.33.2016.09.16.07.04.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 16 Sep 2016 07:04:07 -0700 (PDT) From: Thomas Monjalon To: Bruce Richardson , Jianfeng Tan Cc: dev@dpdk.org, david.marchand@6wind.com, pmatilai@redhat.com, stephen@networkplumber.org Date: Fri, 16 Sep 2016 16:04:06 +0200 Message-ID: <10166504.1OkXfxRTa7@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <20160902165310.GA20356@bricha3-MOBL3> References: <1453661393-85704-1-git-send-email-jianfeng.tan@intel.com> <1472693507-11369-1-git-send-email-jianfeng.tan@intel.com> <20160902165310.GA20356@bricha3-MOBL3> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v3] eal: restrict cores detection 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, 16 Sep 2016 14:04:08 -0000 2016-09-02 17:53, Bruce Richardson: > On Thu, Sep 01, 2016 at 01:31:47AM +0000, Jianfeng Tan wrote: It would help the discussion to have a problem statement here. > > This patch uses pthread_getaffinity_np() to narrow down detected > > cores before parsing coremask (-c), corelist (-l), and coremap > > (--lcores). > > > > The purpose of this patch is to leave out these core related options > > when DPDK applications are deployed under container env, so that > > users only specify core restriction as starting the instance. > > > > Note: previously, some users are using isolated CPUs, which could > > be excluded by default. Please add commands like taskset to use > > those cores. > > > > Test example: > > $ taskset 0xc0000 ./examples/helloworld/build/helloworld -m 1024 > > > > So, to be clear, does this patch mean that DPDK cannot use isolated cores > any more unless you explicitly run the app using taskset? > Is so, NAK, since isolating cores has been part of standard DPDK setup since > the first versions, and I don't believe that we should break that behaviour. So how could we help the container use-case? Any suggestions?