From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vs1-f66.google.com (mail-vs1-f66.google.com [209.85.217.66]) by dpdk.org (Postfix) with ESMTP id 958271B120 for ; Thu, 14 Feb 2019 11:16:39 +0100 (CET) Received: by mail-vs1-f66.google.com with SMTP id t13so3309141vsk.3 for ; Thu, 14 Feb 2019 02:16:39 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Cum6GIYgC082osRwzOQ/4xZ7Znt1/eoekrQLS9RAA9o=; b=rEa2PrASpuIX5Z1U43eEB8bx3QpZ7r9mcE38g9+K94PHEGJEHSxKYf8M54df34IjQf j17o6tF/t+3S/jCQpPsI3iXkhYP4I6tL8gCkRKTRVxOeH88X/cwNJAHFtYLDWxc1/+6c bm8yvY2t0smvu2Y/AAGbLul3t0aoZFnw6JMVs/Y2upaRTX4yJK5pFRt5TixB9nRltJEU HksZ1oLniSt7Tc7/wjCCG/fVUmAzdjuHPNvII0BG+XhA/hcjFAELpuAuEXdrsNVcxoDP Q3LoVvVMmauh7LB8wRg3t1wavf/ZJS1fg73he6a0W2skYdN+5/oCpe5SQk+XhH68hpgW 1/6g== X-Gm-Message-State: AHQUAualQaqOa6R99NFaxhlYkvbXEh/5yWWb40hr6gMW2vkvHF+Pl8Nj GzTAnSA3kaS0qXsMXNdcvERJDISO+82pfl6Feyabgw== X-Google-Smtp-Source: AHgI3IZm7uMX4BF9fZpUNkeNHZgDKLXdg2cr0tinoTSoFx9mnN4PrF/DOONTEHCvD+OpTILZRnrfg94wmqkA+81+Hco= X-Received: by 2002:a67:2045:: with SMTP id g66mr1512875vsg.180.1550139398931; Thu, 14 Feb 2019 02:16:38 -0800 (PST) MIME-Version: 1.0 References: <1550074412-31285-1-git-send-email-david.marchand@redhat.com> <4304821e-dd76-da80-2dec-e1c540e95ea5@intel.com> In-Reply-To: <4304821e-dd76-da80-2dec-e1c540e95ea5@intel.com> From: David Marchand Date: Thu, 14 Feb 2019 11:16:27 +0100 Message-ID: To: "Burakov, Anatoly" Cc: dev@dpdk.org, Olivier Matz , Kevin Traynor , dpdk stable Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] [PATCH] eal: restrict ctrl threads to startup cpu affinity X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Feb 2019 10:16:39 -0000 On Thu, Feb 14, 2019 at 11:05 AM Burakov, Anatoly wrote: > On 14-Feb-19 9:53 AM, David Marchand wrote: > > > A bit more context then, if you want to clearly pin cpu resources for > > the processes on your system (let's say having virtual machines and a > > popular vswitch), I can only think of two solutions. > > Either you have something to configure your processes to have them call > > sched_setaffinity/pthread_set_affinity_np, or you use taskset to get > > them "jailed" without them caring. > > > > Before the incriminated commit, we were keeping all threads on the > > coremask that had been passed, but as Olivier said, we would end up with > > ctrl threads spanwed on core running dataplane threads as well. > > > > Now, the ctrl threads can be spawned anywhere on all & ~coremask, with > > no way to configure this. > > I considered adding a new eal option, but I think relying on the current > > cpu affinity is a better default behavior and I can't see drawbacks at > > the moment. > > OK, that makes sense. However, i feel this behavior (both old and new, > for that matter) should be better documented somewhere in the EAL docs. > > I'll see what I can add in the doc for v2. -- David Marchand