From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shirley Avishour Subject: Re: running dpdk application on the same machine with other none dpdk application Date: Wed, 30 Jan 2019 10:27:31 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Cc: dev@dpdk.org To: Rami Rosen Return-path: Received: from mail-vk1-f196.google.com (mail-vk1-f196.google.com [209.85.221.196]) by dpdk.org (Postfix) with ESMTP id 7999F1B1EA for ; Wed, 30 Jan 2019 09:27:43 +0100 (CET) Received: by mail-vk1-f196.google.com with SMTP id y14so5158053vky.9 for ; Wed, 30 Jan 2019 00:27:43 -0800 (PST) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Rami, This is correct but that is because the default value of the PF_NO_SETAFFINITY flags does not allow to set affinity to kernel threads from user space. I was looking for a way to change the kernel and recompile it to be able to block kernel threads from running on the cpu isolated cores. (same as user space threads). BR, Shirley. On Wed, Jan 30, 2019 at 10:18 AM Rami Rosen wrote: > Hi Shirley, > > > Do you know if the PF_NO_SETAFFINITY flag can help in any way? > > AFAIK, this will not work for kernel thread. > > For example, with 4.8.13-1 kernel: > Display all kernel threads with > ps aux | grep "\["n > > (as kernel threads are enclosed in square brackets, [ ]) > And pick one of them and try: > taskset -pc 7 521 > pid 521's current affinity list: 0-15 > taskset: failed to set pid 521's affinity: Invalid argument > Regards, > Rami Rosen > >