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 D44DB42A03 for ; Wed, 26 Apr 2023 14:19:05 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5768A410FA; Wed, 26 Apr 2023 14:19:05 +0200 (CEST) Received: from office2.cesnet.cz (office2.cesnet.cz [195.113.144.244]) by mails.dpdk.org (Postfix) with ESMTP id CA76740DDA for ; Wed, 26 Apr 2023 14:19:03 +0200 (CEST) Received: from [IPV6:2001:67c:1220:80e:c413:575c:a7cd:cf7b] (unknown [IPv6:2001:67c:1220:80e:c413:575c:a7cd:cf7b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by office2.cesnet.cz (Postfix) with ESMTPSA id 84ACE40008F; Wed, 26 Apr 2023 14:19:03 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cesnet.cz; s=office2-2020; t=1682511543; bh=QVmYgA/UGNqbIBSSYyO2RKmWYeeHeeYcIPGIo6qnWaA=; h=Date:Subject:To:References:From:In-Reply-To; b=BvXxxlo5oKq7AAXqxfJZZ4Kvk46OGsmd+QhTFkiggzHl2RI6ixgljzIZU55qHp6W/ qLXRpTljfpfTAFKUwawrXQXiwc4t6UvwCZ2L1t8jDmiCFeI+/zg9BLTB9M2Z9YXnlr N/JYt6f6tiJkoP+NvnoRgE9PmwK0EEBLPJqogFEBuWyDUIqIZzKXoex4vMdrCjpjEU mfV5n2KZtBUShfTsiU0eiBudd/7iOXHTqaAc5n9yMgK4zMqZY173EHGMv/PLefozfe Yr7lyY+0uFa5Tz3eCIWIAvL38xHxIiL5z5lqIvWJB39uI7pEL4VRWWcZLi0Azqpdk5 vy9F/kRhKUeCg== Message-ID: <704b12cf-e8a3-a3d6-5667-537cd7efe7c5@cesnet.cz> Date: Wed, 26 Apr 2023 14:20:30 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.10.0 Subject: Re: quick question about core affinity Content-Language: en-US To: users@dpdk.org, ljh890322@gmail.com References: From: =?UTF-8?B?THVrw6HFoSDFoGnFoW1pxaE=?= In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Hi, DPDK core affinity runs your application on the selected cores. But that doesn't stop other applications from running on the same cores. To get closer to your goal of really isolating the application from other processes you would need to add isolcpus to your boot parameters. That instructs the scheduler to not use the mentioned cores. After booting with this parameter you could run your DPDK application and scheduler would not schedule any process to the cores that DPDK application would use. However, if you run a separate application and with the taskset command pin it to the cores your DPDK application uses that will still run and will be in conflict with your DPDK app. Best regards, Lukas On 26. 04. 23 13:37, 이재홍 wrote: > Hello, I'm new to DPDK > > I've tried to run samples and got a query about core affinity. > As I understand, if a lcore has affinity to a CPU set, it will run > only on the CPU set. > And I thought If I run a dpdk sample with core 0-2, none process can > use the core (0-2). but when I try to run a simple app(not dpdk app) > with taskset command, it runs on 0, 1, 2 cores.. > > what I want was if I use cores for dpdk apps none other process can > access the cores.. but it seems possible.. > > I've googled to find out this but I couldn't find anything I wanted. > Is there anyone can explain about this...? > > > BR. > Jaehong Lee