From: Mark Zhang <markzhang@nvidia.com>
To: David Ahern <dsahern@gmail.com>, <jgg@nvidia.com>, <dledford@redhat.com>
Cc: <linux-rdma@vger.kernel.org>, <netdev@vger.kernel.org>,
<aharonl@nvidia.com>, <netao@nvidia.com>, <leonro@nvidia.com>
Subject: Re: [PATCH iproute2-next v1 0/3] Optional counter statistics support
Date: Fri, 15 Oct 2021 10:48:29 +0800 [thread overview]
Message-ID: <dca007c3-33bf-0707-9726-46d5ef37db6f@nvidia.com> (raw)
In-Reply-To: <82b34add-ef1e-dc51-3a1c-5fd7777e59ed@gmail.com>
On 10/15/2021 10:28 AM, David Ahern wrote:
> External email: Use caution opening links or attachments
>
>
> On 10/14/21 1:53 AM, Mark Zhang wrote:
>> Change Log:
>> v1:
>> * Add a new nldev command to get the counter status;
>> * Some cosmetic changes.
>> v0: https://lore.kernel.org/all/20210922093038.141905-1-markzhang@nvidia.com/
>>
>> ----------------------------------------------------------------------
>> Hi,
>>
>> This is supplementary part of kernel series [1], which provides an
>> extension to the rdma statistics tool that allows to set or list
>> optional counters dynamically, using netlink.
>>
>> Thanks
>>
>> [1] https://www.spinics.net/lists/linux-rdma/msg106283.html
>>
>
> this has been committed now?
>
Do you mean the kernel series? It was accepted to kernel rdma.git.
next prev parent reply other threads:[~2021-10-15 2:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 7:53 [PATCH iproute2-next v1 0/3] Optional counter statistics support Mark Zhang
2021-10-14 7:53 ` [PATCH iproute2-next v1 1/3] rdma: Update uapi headers Mark Zhang
2021-10-14 7:53 ` [PATCH iproute2-next v1 2/3] rdma: Add stat "mode" support Mark Zhang
2021-10-15 23:56 ` David Ahern
2021-10-16 7:14 ` Maor Gottlieb
2021-10-14 7:53 ` [PATCH iproute2-next v1 3/3] rdma: Add optional-counters set/unset support Mark Zhang
2021-10-15 2:28 ` [PATCH iproute2-next v1 0/3] Optional counter statistics support David Ahern
2021-10-15 2:48 ` Mark Zhang [this message]
2021-10-16 18:53 ` David Ahern
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=dca007c3-33bf-0707-9726-46d5ef37db6f@nvidia.com \
--to=markzhang@nvidia.com \
--cc=aharonl@nvidia.com \
--cc=dledford@redhat.com \
--cc=dsahern@gmail.com \
--cc=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netao@nvidia.com \
--cc=netdev@vger.kernel.org \
/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