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 954B6A0543; Fri, 7 Oct 2022 21:49:14 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 7549E400D5; Fri, 7 Oct 2022 21:49:14 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 4CF6F40042 for ; Fri, 7 Oct 2022 21:49:13 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1665172152; 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: in-reply-to:in-reply-to:references:references; bh=flWc4b5I2OXTy3peLVcDtSmRPpAxaV5k6JRRQqs5OIU=; b=TYt75j61TgsRf/mz/1kkNpUnQnjfqItp6PiZxHpKLs2/66JGZbLSnRKr1fOpXnGT/qv3B3 bNZUEXIH5Q0U63PLge0thYudvXgbnbEf1bavzjekPah+3jjs71kwamWqEbl/9IPguPY0zT CheDh2372xQDzb3SFRfjbIRtIboa040= Received: from mail-pg1-f197.google.com (mail-pg1-f197.google.com [209.85.215.197]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-468-Kb8uonUdN1C6W7ugYAmM8w-1; Fri, 07 Oct 2022 15:49:11 -0400 X-MC-Unique: Kb8uonUdN1C6W7ugYAmM8w-1 Received: by mail-pg1-f197.google.com with SMTP id x23-20020a634857000000b0043c700f6441so3400326pgk.21 for ; Fri, 07 Oct 2022 12:49:11 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=flWc4b5I2OXTy3peLVcDtSmRPpAxaV5k6JRRQqs5OIU=; b=F4XgK7Uc6jnsTUVmCj+jBQ+iLL+IrTBtEQ6pdsSweA3fAaAFNTNQJ18dUm8a5LcJYB EbcDjxaSfzxWn34wAw0ydqcG7QztXyNvWN31bRHq7EauhNdvnwZ6Jt6s3H3BpVM3W35z WluA8IoVngOsO2A1R6b9YVa4QR5JthmCIFPc8xEgQo3vi1n5Dplce6UNqvQkJrss2KyD QsEmpD3INy1bzSqM3ISbD7K14cwU395cc/7nuxYlrOUk2RybFX5wISw/tghzHZE+tiXv TR2tJ0xRTYKqp+zKY6Mbp2NBFRREZ9fgoqT1OcT2ZA0Yhr8dMhF7gd7L85zJ/tVl9M+/ 4XJw== X-Gm-Message-State: ACrzQf05r5lNOs3sbuy3vSNxQz8MeqJyR8JsDrBC4jcvV4FE/2k+ZG+g 5t+QB8n4vto8b1NRkVt/OJbBvXGE3CDqKvAlHcsxF9TIt8mmyzLiIZ7xRtfyZhS5g5ed7ndqZG7 +O5gHzackVZ+96wYPsP0= X-Received: by 2002:a17:902:bf46:b0:179:eba5:90ba with SMTP id u6-20020a170902bf4600b00179eba590bamr6349039pls.16.1665172150761; Fri, 07 Oct 2022 12:49:10 -0700 (PDT) X-Google-Smtp-Source: AMsMyM7PME9ZnZPy+csPq7tSvjFL8txwTdlq6a6AsxI+el6vAd0wr2WyMa5q/bxGlJOPJ0xzYe9HCxG2N4Xc2OTT78U= X-Received: by 2002:a17:902:bf46:b0:179:eba5:90ba with SMTP id u6-20020a170902bf4600b00179eba590bamr6349016pls.16.1665172150516; Fri, 07 Oct 2022 12:49:10 -0700 (PDT) MIME-Version: 1.0 References: <20220525103352.1806937-1-amitprakashs@marvell.com> <20220929114313.1346972-1-amitprakashs@marvell.com> In-Reply-To: <20220929114313.1346972-1-amitprakashs@marvell.com> From: David Marchand Date: Fri, 7 Oct 2022 21:48:59 +0200 Message-ID: Subject: Re: [PATCH v5 1/2] mem: telemetry support for memseg and element information To: Amit Prakash Shukla , Anatoly Burakov , dmitry.kozliuk@gmail.com Cc: dev@dpdk.org, jerinj@marvell.com, bruce.richardson@intel.com, ciara.power@intel.com, Thomas Monjalon X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Thu, Sep 29, 2022 at 1:43 PM Amit Prakash Shukla wrote: > 4. /eal/element_list,,, > The command outputs number of elements in a memseg based > on the heap-id, memseg-list-id and memseg-id given as input. > Example: > --> /eal/element_list,0,0,63 > {"/eal/element_list": {"Element_count": 52}} > > --> /eal/element_list,0,1,15 > {"/eal/element_list": {"Element_count": 52}} > > 5. /eal/element_info,,,, \ > , > The command outputs element information like element start > address, end address, to which memseg it belongs, element > state, element size. User can give a range of elements to be > printed. > Example: > --> /eal/element_info,0,1,15,1,2 > {"/eal/element_info": {"element.1": {"msl_id": 1, \ > "ms_id": 15, "memseg_start_addr": "0xb20000000", \ > "memseg_end_addr": "0xb40000000", \ > "element_start_addr": "0xb201fe680", \ > "element_end_addr": "0xb20bfe700", \ > "element_size": 10485888, "element_state": "Busy"}, \ > "element.2": {"msl_id": 1, "ms_id": 15, \ > "memseg_start_addr": "0xb20000000", \ > "memseg_end_addr": "0xb40000000", \ > "element_start_addr": "0xb20bfe700", \ > "element_end_addr": "0xb215fe780", "element_size": 10485888, \ > "element_state": "Busy"}, "Element_count": 2}} > element is too generic. Just look at the command name: /eal/element_XXX. What is an EAL element? -- David Marchand