From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <thomas@monjalon.net> Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id C91372B8E for <dev@dpdk.org>; Tue, 25 Apr 2017 13:01:02 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 47CEC20496; Tue, 25 Apr 2017 07:01:02 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 25 Apr 2017 07:01:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=OixUoNs1ZyjVsfs hU7Nnlr68CBxdoPowBvGH6afAhvE=; b=qIcEDhYAPumObMImAOVUvHZt5pKkg3h pqB7tifA7rdPSxuEW1G+tYFkZnfturaBJ0UPvAEX0/0XagKl5gV06c+sr8bOSQDE PhuNXLR6wzvFXrkOzS7M0ASnDeB5ChSZL90DMVCLLVFEiKO/JdWtyNOOfK9OzNsF y3c4akSZ272Y= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=OixUoNs1ZyjVsfshU7Nnlr68CBxdoPowBvGH6afAhvE=; b=UeZcCg/G iQiBcwcVfiEJk+0PDTWXn4NPSLOb0DbIeQCq3W8/qsluxTdkyVLuwlTpWmMtxlRO rOJbwtuP6D/Is9RYIa+GWxaL6qI8uTnj8q1v8TzgVWKsI0GZgCmDM8uPDUDuv0pr ha40qn/bbhkTEyvDRrDHOsn+GtRtFxAJqXI8mKXCnqHTkFl55Tnad4D8rJqqzXP5 XGY7tEHCP2bwmjepi7yWRRrDb+UNIDmTwJl2IekuP6SRLq/3pt3yLdIjEUGlybbi yYb7rN+XYMf5Muvj9ZNk1lHsBnyzVumof+CwfBdeGr9D17YzjvXQzwj9z0mDmzPq 95tVJ6ZuIcsxWQ== X-ME-Sender: <xms:biz_WDufov2lDnOZ1xhm7cjmuSwVXZCvLtvVYxRY6TOyYJKl19s04g> X-Sasl-enc: tipLsaxmByviEbZr+GQ8sAR21w8UJS2g6ZkfTM6u/TcE 1493118061 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id B07837E320; Tue, 25 Apr 2017 07:01:01 -0400 (EDT) From: Thomas Monjalon <thomas@monjalon.net> To: Andriy Berestovskyy <Andriy.Berestovskyy@caviumnetworks.com> Cc: dev@dpdk.org Date: Tue, 25 Apr 2017 13:01:00 +0200 Message-ID: <1682863.QcTJhb8gfk@xps> In-Reply-To: <a98eb80c-ff04-224d-a8c7-41323c44035c@caviumnetworks.com> References: <1490962860-11567-1-git-send-email-Andriy.Berestovskyy@caviumnetworks.com> <1810447.5BRUVpxoUJ@xps> <a98eb80c-ff04-224d-a8c7-41323c44035c@caviumnetworks.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] usertools: use /sys/devices/system/cpu for CPU layout script X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Tue, 25 Apr 2017 11:01:03 -0000 25/04/2017 12:19, Andriy Berestovskyy: > Hi, > > On 25.04.2017 10:48, Thomas Monjalon wrote: > > Do you think it is really a good idea to keep and maintain this script > > in DPDK? It was intentionnally not exported in "make install". > > I think it is a bit out of scope, and I wonder which alternatives > > do we have? I know hwloc/lstopo, but there are probably others. > > hwloc does not work on my target, but you are right, there are a variety > of tools for that. For example, I prefer numactl (option -H) because it > also allows to do many useful things, like bind CPUs to one node and > memory allocations to another. > > At the moment the script is just like the lscpu, which is preinstalled > on Ubuntu and mentioned in the documentation alongside with the cpu_layout. > > We could try to make the script more useful, for example, show which NIC > is on which NUMA node. Still, it will be just a subset of functionality > of tools like hwloc... Yes. The other idea would be to properly document existing tools and remove this one. Opinions?