DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org, maryam.tahhan@intel.com, reshma.pattan@intel.com
Subject: Re: [dpdk-dev] [PATCH v2] app/procinfo: enhance port mempool and crypto info
Date: Sat, 11 Jul 2020 20:12:24 -0700	[thread overview]
Message-ID: <20200711201224.6fc4eca1@hermes.lan> (raw)
In-Reply-To: <20200711095343.10523-1-hemant.agrawal@nxp.com>

On Sat, 11 Jul 2020 15:23:43 +0530
Hemant Agrawal <hemant.agrawal@nxp.com> wrote:

> This patch enhances the port info for more details about
> the port and queues.
> This patch also add support to get info about the mempool
> ops and security context for crypto devices.
> 
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>

What ever happened to my procinfo patch series.


https://patchwork.dpdk.org/patch/69877/

  reply	other threads:[~2020-07-12  3:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10 16:06 [dpdk-dev] [PATCH] app/procinfo: enhance port and mempool info Hemant Agrawal
2020-07-10 18:07 ` Stephen Hemminger
2020-07-11  9:53 ` [dpdk-dev] [PATCH v2] app/procinfo: enhance port mempool and crypto info Hemant Agrawal
2020-07-12  3:12   ` Stephen Hemminger [this message]
2020-07-13  3:49     ` Hemant Agrawal
2020-07-15  0:07       ` Stephen Hemminger
2020-07-15  0:43         ` Hemant Agrawal
2020-07-13  9:57   ` Pattan, Reshma
2020-07-13 13:15   ` [dpdk-dev] [PATCH v3 1/2] app/proc-info: enhance mempool to print ops name Hemant Agrawal
2020-07-13 13:15     ` [dpdk-dev] [PATCH v3 2/2] app/proc-info: add crypto security context info Hemant Agrawal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200711201224.6fc4eca1@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=maryam.tahhan@intel.com \
    --cc=reshma.pattan@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).