From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH] kni: add module parameter 'bind_to_core' Date: Thu, 25 Aug 2016 15:46:46 +0100 Message-ID: <57BF04D6.9040108@intel.com> References: <20160816182455.4809-1-vladyslav.buslov@harmonicinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Vladyslav Buslov Return-path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id EA85F5584 for ; Thu, 25 Aug 2016 16:46:55 +0200 (CEST) In-Reply-To: <20160816182455.4809-1-vladyslav.buslov@harmonicinc.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Vladyslav, On 8/16/2016 7:24 PM, Vladyslav Buslov wrote: > Allow binding KNI thread to specific core in single threaded mode. I think this is good idea. But I am not sure about making this a module parameter, setting core can be more dynamic. There is already a kni->core_id field, which is only used for multiple_kthread mode. What do you think moving single thread creation into kni_ioctl_create() and use first kni->core_id to bind the thread? If there is no kni->core_id set, it will behave as it is now. > > Signed-off-by: Vladyslav Buslov > --- <...>