From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 5A2B7A058B; Wed, 25 Mar 2020 13:53:42 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id A95232BAE; Wed, 25 Mar 2020 13:53:41 +0100 (CET) Received: from us-smtp-delivery-74.mimecast.com (us-smtp-delivery-74.mimecast.com [63.128.21.74]) by dpdk.org (Postfix) with ESMTP id 56CB53B5 for ; Wed, 25 Mar 2020 13:53:40 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1585140819; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=vEKo1SScUzVcGX3l43vdJsMbtVIOMvmLXqF1Mkp5F3Q=; b=Bz0/XYksrya6rKOmZqXhn2wBa945g76C6NovzI/mLIGzy7wTNTEiDCx2TF+FdkN8jTjuHD 0tbY+cXPASAihTh/3PNh9Hn0Pq/VecQ00YWqflcUsW+ipLYVL9g/PSzVqw+sK76UoZx4x4 lSgh4ydlU6vZQ5fx/lU0UiILJ42Mn0g= Received: from mail-vs1-f69.google.com (mail-vs1-f69.google.com [209.85.217.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-462-U-LWYqiRMjakZFvLEOQxnQ-1; Wed, 25 Mar 2020 08:53:38 -0400 X-MC-Unique: U-LWYqiRMjakZFvLEOQxnQ-1 Received: by mail-vs1-f69.google.com with SMTP id m24so251284vsj.14 for ; Wed, 25 Mar 2020 05:53:38 -0700 (PDT) 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=KwcAunLufvsN5porAuYDcYaikcTp6S+8A6rexH5VLJo=; b=ofB/RSUusk0V66j5fEgvJygTJBSnWsk3Fm/vydF6YMN1sHgRLVGXwbbjiTl371vsZi 1CEOV7kr4rtL8rDH8ljz6ewXDE4/lMzisu69MtnzdsQQt3ua1SCJyThcAmvyc/PSqey4 HgPrZyW5gQGTY9Wvjteh24ETy0MJyGt/FE55xuWWETwUKI2aQdGX0BzMx1AIm04R+spK BZDxmYZ3AY5lN/1xnGruy2fuMDJs9qSm3N2ahX92jCU4mDkWUkP3vCkpCrJQaunMRMbR m4XB4llgM26mufeRVZNs6Gg0HE2YajNQyf771FTIDqbjuhqbDB7lMe4u8iewNbwRab3G iqYw== X-Gm-Message-State: ANhLgQ1SGP8BKYQUsk9B+lNp39RljI1URNr+xzhE1d/Bo0fFw35gTeVO cB57Pyn+6vHItxNRgxMCPyeQsrSCgXOGjQBbkpqcHAII4cx66UpAj/UVFaCgnm5Ic+XE2DWI8BY wq9yA5TZV9llfY91OkwI= X-Received: by 2002:a67:2c81:: with SMTP id s123mr1178106vss.198.1585140817530; Wed, 25 Mar 2020 05:53:37 -0700 (PDT) X-Google-Smtp-Source: ADFU+vso2BI+WvUHZ4jL5Gk10shXzcyjPStEOxmgq2ezp2FptyWjDt8GJxiQkKLjhzZ0LfuXs0+hl8E8swi+2AA4poc= X-Received: by 2002:a67:2c81:: with SMTP id s123mr1178095vss.198.1585140817279; Wed, 25 Mar 2020 05:53:37 -0700 (PDT) MIME-Version: 1.0 References: <20200205102416.698395-1-jerinj@marvell.com> In-Reply-To: From: David Marchand Date: Wed, 25 Mar 2020 13:53:26 +0100 Message-ID: To: Jerin Jacob Kollanukkaran Cc: dev , Olivier Matz X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Subject: Re: [dpdk-dev] [PATCH] eal: store control thread CPU affinity in TLS 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Fri, Mar 13, 2020 at 9:34 AM David Marchand wrote: > On Wed, Feb 5, 2020 at 11:24 AM wrote: > > > > From: Jerin Jacob > > > > _cpuset TLS variable stores the CPU affinity of eal thread. > > Populate the _cpuset TLS variable for control thread to > > > > 1) Make rte_thread_get_affinity() and eal_thread_dump_affinity > > functional with control thread. > > 2) Quick access to cpu affinity. > > > > Signed-off-by: Jerin Jacob > Reviewed-by: David Marchand Applied, thanks. --=20 David Marchand