From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 2F7F9A0550; Tue, 16 Feb 2021 11:53:03 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id A974716070C; Tue, 16 Feb 2021 11:53:02 +0100 (CET) Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by mails.dpdk.org (Postfix) with ESMTP id B817140690 for ; Tue, 16 Feb 2021 11:53:00 +0100 (CET) IronPort-SDR: Ayn1AU0h6AVB2Y9UEKJ6N/8/RgSfZLugGyDjRnOQJ5D/YrU1+SmvwMkHmDTbPxmjvWb+DKVyf5 k5zYG5pc7SLA== X-IronPort-AV: E=McAfee;i="6000,8403,9896"; a="267703463" X-IronPort-AV: E=Sophos;i="5.81,183,1610438400"; d="scan'208";a="267703463" Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Feb 2021 02:52:59 -0800 IronPort-SDR: QcEmYwJNUexQMHsvdBso9XrWfu3j80aHqwD7bYOPPWOMrGYp6LjJxCn07GvRzrKZRHSDNY1vUH OKLW0TV1wtIA== X-IronPort-AV: E=Sophos;i="5.81,183,1610438400"; d="scan'208";a="399461122" Received: from wardmich-mobl.ger.corp.intel.com (HELO [10.213.232.191]) ([10.213.232.191]) by orsmga008-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 16 Feb 2021 02:52:58 -0800 To: Bruce Richardson , Harry van Haaren Cc: dev@dpdk.org References: <20210216094300.27889-1-bruce.richardson@intel.com> <313c223f-bf1c-9307-75f8-0a0c1da7fd21@intel.com> <20210216104652.GB136@bricha3-MOBL.ger.corp.intel.com> From: "Burakov, Anatoly" Message-ID: <42706d4c-f8de-55c5-1161-b1e54c77599e@intel.com> Date: Tue, 16 Feb 2021 10:52:56 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: <20210216104652.GB136@bricha3-MOBL.ger.corp.intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH] eal: support using 0 as coremask for no-affinitization X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 16-Feb-21 10:46 AM, Bruce Richardson wrote: > On Tue, Feb 16, 2021 at 10:36:13AM +0000, Burakov, Anatoly wrote: >> On 16-Feb-21 9:43 AM, Bruce Richardson wrote: >>> Allow the user to specify that they don't want any core pinning from DPDK >>> by passing in the coremask of 0. >>> --- >> >> I haven't checked what happens yet, but down the line we also set affinity >> for service cores as well as interrupt thread. what would be the semantics >> of those in this particular case? do we want the same ability for service >> cores (i.e. pick a non-affinitized core)? And where does interrupt thread >> affinitize in this case (presumably, nowhere too)? >> > I have not checked the service core setup, because a) I forgot about them > and b) I'm not sure how their affinity rules work with respect to the main > lcore mask. On the other hand I did check out that the lcore mask for all > non-pinned threads, or control threads, is the full set of bits as > expected. > > /Bruce > +Harry, I believe service core mask must not overlap with lcore masks, so presumably using 0 as lcore mask would make it so that any service core mask will be valid (which is presumably what we want?). Should service cores also have a "just pick a core" parameter? I'm assuming this use-case is explicitly avoiding the CPU/memory/NIA NUMA affinity question, so i'm not bringing it up :) -- Thanks, Anatoly