public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: zhenwei pi <zhenwei.pi@linux.dev>
To: Zhu Yanjun <yanjun.zhu@linux.dev>,
	linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org
Cc: zyjzyj2000@gmail.com, jgg@ziepe.ca, leon@kernel.org
Subject: Re: [PATCH 3/3] RDMA/rxe: support perf mgmt
Date: Sun, 29 Mar 2026 10:53:41 +0800	[thread overview]
Message-ID: <f40973fe-3b40-4e46-a932-11ab3f6ae13e@linux.dev> (raw)
In-Reply-To: <5dadbcdd-3332-45d2-941f-c9d057cd8ea5@linux.dev>



On 3/29/26 00:56, Zhu Yanjun wrote:
> 在 2026/3/28 2:28, zhenwei pi 写道:
>> In RXE, hardware counters are already supported, but not in a
>> standardized manner. For instance, user-space monitoring tools like
>> atop only read from the *counters* directory. Therefore, it is
>> necessary to add perf management support to RXE.
>>
>> Signed-off-by: zhenwei pi <zhenwei.pi@linux.dev>
>> ---
>>   drivers/infiniband/sw/rxe/Makefile    |  1 +
>>   drivers/infiniband/sw/rxe/rxe_loc.h   |  6 ++
>>   drivers/infiniband/sw/rxe/rxe_mad.c   | 86 +++++++++++++++++++++++++++
>>   drivers/infiniband/sw/rxe/rxe_verbs.c |  1 +
>>   drivers/infiniband/sw/rxe/rxe_verbs.h |  5 ++
>>   5 files changed, 99 insertions(+)
>>   create mode 100644 drivers/infiniband/sw/rxe/rxe_mad.c
>>
>> diff --git a/drivers/infiniband/sw/rxe/Makefile b/drivers/infiniband/ 
>> sw/rxe/Makefile
>> index 93134f1d1d0c..3c47e5b982c2 100644
>> --- a/drivers/infiniband/sw/rxe/Makefile
>> +++ b/drivers/infiniband/sw/rxe/Makefile
>> @@ -22,6 +22,7 @@ rdma_rxe-y := \
>>       rxe_mcast.o \
>>       rxe_task.o \
>>       rxe_net.o \
>> +    rxe_mad.o \
>>       rxe_hw_counters.o
>>   rdma_rxe-$(CONFIG_INFINIBAND_ON_DEMAND_PAGING) += rxe_odp.o
>> diff --git a/drivers/infiniband/sw/rxe/rxe_loc.h b/drivers/infiniband/ 
>> sw/rxe/rxe_loc.h
>> index 7992290886e1..a8ce85147c1f 100644
>> --- a/drivers/infiniband/sw/rxe/rxe_loc.h
>> +++ b/drivers/infiniband/sw/rxe/rxe_loc.h
>> @@ -245,4 +245,10 @@ static inline int rxe_ib_advise_mr(struct ib_pd *pd,
>>   #endif /* CONFIG_INFINIBAND_ON_DEMAND_PAGING */
>> +/* rxe-mad.c */
>> +int rxe_process_mad(struct ib_device *ibdev, int mad_flags, u32 
>> port_num,
>> +            const struct ib_wc *in_wc, const struct ib_grh *in_grh,
>> +            const struct ib_mad *in, struct ib_mad *out,
>> +            size_t *out_mad_size, u16 *out_mad_pkey_index);
>> +
>>   #endif /* RXE_LOC_H */
>> diff --git a/drivers/infiniband/sw/rxe/rxe_mad.c b/drivers/infiniband/ 
>> sw/rxe/rxe_mad.c
>> new file mode 100644
>> index 000000000000..9148f384b05c
>> --- /dev/null
>> +++ b/drivers/infiniband/sw/rxe/rxe_mad.c
>> @@ -0,0 +1,86 @@
>> +// SPDX-License-Identifier: GPL-2.0 OR Linux-OpenIB
>> +/*
>> + * Copyright (c) 2026 zhenwei pi <zhenwei.pi@linux.dev>
>> + */
>> +
>> +#include <rdma/ib_pma.h>
>> +#include "rxe.h"
>> +#include "rxe_hw_counters.h"
>> +
>> +static int rxe_process_pma_info(struct ib_mad *out)
>> +{
>> +    struct ib_class_port_info cpi = {};
>> +
>> +    cpi.capability_mask = IB_PMA_CLASS_CAP_EXT_WIDTH;
>> +    memcpy((out->data + 40), &cpi, sizeof(cpi));
>> +
>> +    return IB_MAD_RESULT_SUCCESS | IB_MAD_RESULT_REPLY;
>> +}
>> +
>> +static int rxe_process_pma_counters(struct rxe_dev *rxe, struct 
>> ib_mad *out)
>> +{
>> +    struct ib_pma_portcounters *pma_cnt =
>> +        (struct ib_pma_portcounters *)(out->data + 40);
>> +
>> +    pma_cnt->link_downed_counter = rxe_counter_get(rxe, 
>> RXE_CNT_LINK_DOWNED);
>> +
>> +    return IB_MAD_RESULT_SUCCESS | IB_MAD_RESULT_REPLY;
>> +}
>> +
>> +static int rxe_process_pma_counters_ext(struct rxe_dev *rxe, struct 
>> ib_mad *out)
>> +{
>> +    struct ib_pma_portcounters_ext *pma_cnt_ext =
>> +        (struct ib_pma_portcounters_ext *)(out->data + 40);
>> +
>> +    pma_cnt_ext->port_xmit_data = cpu_to_be64(rxe_counter_get(rxe, 
>> RXE_CNT_SENT_BYTES) >> 2);
>> +    pma_cnt_ext->port_rcv_data = cpu_to_be64(rxe_counter_get(rxe, 
>> RXE_CNT_RCVD_BYTES) >> 2);
>> +    pma_cnt_ext->port_xmit_packets = cpu_to_be64(rxe_counter_get(rxe, 
>> RXE_CNT_SENT_PKTS));
>> +    pma_cnt_ext->port_rcv_packets = cpu_to_be64(rxe_counter_get(rxe, 
>> RXE_CNT_RCVD_PKTS));
> 
> In rxe_process_pma_counters_ext, cpu_to_be64() is used to calculate the 
> 64-bit counters.
> 
> But in rxe_process_pma_counters, pma_cnt->link_downed_counter = 
> rxe_counter_get(), this misses the endianness conversion. The IB spec 
> requires MAD data to be in Big Endian.
> 
> struct ib_pma_portcounters {
>      u8 reserved;
>      u8 port_select;
>      __be16 counter_select;
>      __be16 symbol_error_counter;
>      u8 link_error_recovery_counter;
>      u8 link_downed_counter;           <--- It is u8.
>      __be16 port_rcv_errors;
>      __be16 port_rcv_remphys_errors;
>      __be16 port_rcv_switch_relay_errors;
>      __be16 port_xmit_discards;
>      u8 port_xmit_constraint_errors;
>      u8 port_rcv_constraint_errors;
>      u8 reserved1;
>      u8 link_overrun_errors; /* LocalLink: 7:4, BufferOverrun: 3:0 */
>      __be16 reserved2;
>      __be16 vl15_dropped;
>      __be32 port_xmit_data;
>      __be32 port_rcv_data;
>      __be32 port_xmit_packets;
>      __be32 port_rcv_packets;
>      __be32 port_xmit_wait;
> } __packed;
> 
> Please fix it.

OK.

> 
>> +
>> +    return IB_MAD_RESULT_SUCCESS | IB_MAD_RESULT_REPLY;
>> +}
>> +
>> +static int rxe_process_perf_mgmt(struct rxe_dev *rxe, const struct 
>> ib_mad *in,
>> +                 struct ib_mad *out)
>> +{
>> +    switch (in->mad_hdr.attr_id) {
>> +    case IB_PMA_CLASS_PORT_INFO:
>> +        return rxe_process_pma_info(out);
>> +
>> +    case IB_PMA_PORT_COUNTERS:
>> +        return rxe_process_pma_counters(rxe, out);
>> +
>> +    case IB_PMA_PORT_COUNTERS_EXT:
>> +        return rxe_process_pma_counters_ext(rxe, out);
>> +
>> +    default:
>> +        break;
>> +    }
>> +
>> +    return IB_MAD_RESULT_FAILURE;
>> +}
>> +
>> +int rxe_process_mad(struct ib_device *ibdev, int mad_flags, u32 
>> port_num,
>> +            const struct ib_wc *in_wc, const struct ib_grh *in_grh,
>> +            const struct ib_mad *in, struct ib_mad *out,
>> +            size_t *out_mad_size, u16 *out_mad_pkey_index)
>> +{
>> +    struct rxe_dev *rxe = to_rdev(ibdev);
>> +    u8 mgmt_class = in->mad_hdr.mgmt_class;
>> +    u8 method = in->mad_hdr.method;
>> +
>> +    if (port_num != RXE_PORT)
>> +        return IB_MAD_RESULT_FAILURE;
>> +
>> +    switch (mgmt_class) {
>> +    case IB_MGMT_CLASS_PERF_MGMT:
>> +        if (method == IB_MGMT_METHOD_GET)
> 
> The function rxe_process_mad receives *in* MAD and populates the *out* 
> MAD. Since the out buffer is eventually transmitted back to the caller— 
> which could be a user-space application or a remote node on the network— 
> it is important to ensure that any unassigned bytes (padding) within the 
> out packet are initialized to zero. If the underlying framework does not 
> pre-zero the out memory, areas outside of the memcpy((out->data + 40), 
> &cpi, sizeof(cpi)) call could inadvertently leak sensitive residual 
> kernel data.
> 
> Thus add this line in the function before filling in data:
> 
> memset(out->data, 0, 256);
> 
> 256 is the length of out->data, please adjust this number based on the 
> actual data length.
> 

I notice that all of the callers use kzalloc to allocate out MAD data, 
so there is no need to clear it again. In addition, other drivers like 
mlx5 does not clear memory too.
I also have no objection to clear buffer in RXE, please let me know if 
it's necessary.

> Please also consider adding support for IB_MGMT_METHOD_SET. This would 
> allow the user space application to clear or reset specific metrics by 
> calling atomic64_set(..., 0) on the underlying RXE counters.
> 

Sure, I'll rename functions, for example, rename 'rxe_process_perf_mgmt' 
to 'rxe_get_perf_mgmt'. 'rxe_set_perf_mgmt' will be supported in the 
future easily. I'm not going to support SET method in this serries 
because of the lack of *store* opeation from these sysfs attributes.

Yanjun, thanks!

> Thanks a lot.
> Zhu Yanjun
>> +            return rxe_process_perf_mgmt(rxe, in, out);
>> +        break;
>> +
>> +    default:
>> +        break;
>> +    }
>> +
>> +    return IB_MAD_RESULT_FAILURE;
>> +}
>> diff --git a/drivers/infiniband/sw/rxe/rxe_verbs.c b/drivers/ 
>> infiniband/sw/rxe/rxe_verbs.c
>> index bcd486e8668b..7df0cb5a09a3 100644
>> --- a/drivers/infiniband/sw/rxe/rxe_verbs.c
>> +++ b/drivers/infiniband/sw/rxe/rxe_verbs.c
>> @@ -1509,6 +1509,7 @@ static const struct ib_device_ops rxe_dev_ops = {
>>       .post_recv = rxe_post_recv,
>>       .post_send = rxe_post_send,
>>       .post_srq_recv = rxe_post_srq_recv,
>> +    .process_mad = rxe_process_mad,
>>       .query_ah = rxe_query_ah,
>>       .query_device = rxe_query_device,
>>       .query_pkey = rxe_query_pkey,
>> diff --git a/drivers/infiniband/sw/rxe/rxe_verbs.h b/drivers/ 
>> infiniband/sw/rxe/rxe_verbs.h
>> index 2bcfb919a40b..1c4fa8eaa733 100644
>> --- a/drivers/infiniband/sw/rxe/rxe_verbs.h
>> +++ b/drivers/infiniband/sw/rxe/rxe_verbs.h
>> @@ -466,6 +466,11 @@ static inline void rxe_counter_add(struct rxe_dev 
>> *rxe, enum rxe_counters index,
>>       atomic64_add(val, &rxe->stats_counters[index]);
>>   }
>> +static inline s64 rxe_counter_get(struct rxe_dev *rxe, enum 
>> rxe_counters index)
>> +{
>> +    return atomic64_read(&rxe->stats_counters[index]);
>> +}
>> +
>>   static inline struct rxe_dev *to_rdev(struct ib_device *dev)
>>   {
>>       return dev ? container_of(dev, struct rxe_dev, ib_dev) : NULL;
> 


      reply	other threads:[~2026-03-29  2:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-28  9:28 [PATCH 0/3] Support PERF MGMT for RXE zhenwei pi
2026-03-28  9:28 ` [PATCH 1/3] RDMA/rxe: use RXE_PORT instead of magic number 1 zhenwei pi
2026-03-28  9:28 ` [PATCH 2/3] RDMA/rxe: add SENT/RCVD bytes zhenwei pi
2026-03-28 18:02   ` Zhu Yanjun
2026-03-28  9:28 ` [PATCH 3/3] RDMA/rxe: support perf mgmt zhenwei pi
2026-03-28 16:56   ` Zhu Yanjun
2026-03-29  2:53     ` zhenwei pi [this message]

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=f40973fe-3b40-4e46-a932-11ab3f6ae13e@linux.dev \
    --to=zhenwei.pi@linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=yanjun.zhu@linux.dev \
    --cc=zyjzyj2000@gmail.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