From: "humin (Q)" <humin29@huawei.com>
To: Chengwen Feng <fengchengwen@huawei.com>, <thomas@monjalon.net>,
<ferruh.yigit@xilinx.com>
Cc: <dev@dpdk.org>, <chas3@att.com>
Subject: Re: [PATCH v2 0/3] net/bonding: support device private dump
Date: Wed, 14 Dec 2022 17:55:21 +0800 [thread overview]
Message-ID: <83aae131-14f0-72b8-4dac-792abc6bb52f@huawei.com> (raw)
In-Reply-To: <20221214061325.20272-1-fengchengwen@huawei.com>
Acked-by:Min Hu (Connor) <humin29@huawei.com>
在 2022/12/14 14:13, Chengwen Feng 写道:
> This patchset adds device private dump for bonding PMD, and use
> rte_eth_dev_priv_dump API to implement testpmd show bonding command.
>
> Chengwen Feng (3):
> net/bonding: support private dump ops
> net/bonding: support dump LACP info
> net/bonding: use dump API to impl show bonding cmd
>
> ---
> v2:
> * address Min Hu's comment
> * use rte_eth_dev_priv_dump API to implement testpmd show bonding
> command.
>
> .../link_bonding_poll_mode_drv_lib.rst | 13 +-
> drivers/net/bonding/bonding_testpmd.c | 281 +-----------------
> drivers/net/bonding/rte_eth_bond_pmd.c | 244 ++++++++++++++-
> 3 files changed, 249 insertions(+), 289 deletions(-)
>
next prev parent reply other threads:[~2022-12-14 9:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 8:10 [PATCH 0/2] " Chengwen Feng
2022-12-05 8:10 ` [PATCH 1/2] net/bonding: support private dump ops Chengwen Feng
2022-12-06 2:01 ` humin (Q)
2022-12-14 6:24 ` fengchengwen
2022-12-05 8:10 ` [PATCH 2/2] net/bonding: support dump LACP info Chengwen Feng
2022-12-14 6:13 ` [PATCH v2 0/3] net/bonding: support device private dump Chengwen Feng
2022-12-14 6:13 ` [PATCH v2 1/3] net/bonding: support private dump ops Chengwen Feng
2022-12-14 6:13 ` [PATCH v2 2/3] net/bonding: support dump LACP info Chengwen Feng
2022-12-14 6:13 ` [PATCH v2 3/3] net/bonding: use dump API to impl show bonding cmd Chengwen Feng
2022-12-14 9:55 ` humin (Q) [this message]
2022-12-15 10:56 ` [PATCH v2 0/3] net/bonding: support device private dump lihuisong (C)
2023-01-16 12:34 ` Ferruh Yigit
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=83aae131-14f0-72b8-4dac-792abc6bb52f@huawei.com \
--to=humin29@huawei.com \
--cc=chas3@att.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=ferruh.yigit@xilinx.com \
--cc=thomas@monjalon.net \
/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).