From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: zhenwei pi <zhenwei.pi@linux.dev>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
"yanjun.zhu@linux.dev" <yanjun.zhu@linux.dev>
Cc: zyjzyj2000@gmail.com, jgg@ziepe.ca, leon@kernel.org
Subject: Re: [PATCH v2 4/4] RDMA/rxe: use rxe_counter_get
Date: Sat, 28 Mar 2026 21:56:19 -0700 [thread overview]
Message-ID: <3cb474cf-4610-4dc6-b87f-83a9d26122ed@linux.dev> (raw)
In-Reply-To: <20260329025552.122946-5-zhenwei.pi@linux.dev>
在 2026/3/28 19:55, zhenwei pi 写道:
> There is *rxe_counter_get* helper in RXE, use it instead of raw
> atomic64_read.
This commit can be merged with the commit "[PATCH v2 3/4] RDMA/rxe:
support perf mgmt GET method"
Zhu Yanjun
>
> Signed-off-by: zhenwei pi <zhenwei.pi@linux.dev>
> ---
> drivers/infiniband/sw/rxe/rxe_hw_counters.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/sw/rxe/rxe_hw_counters.c b/drivers/infiniband/sw/rxe/rxe_hw_counters.c
> index 17edaa9a9b9b..a612e96f7a88 100644
> --- a/drivers/infiniband/sw/rxe/rxe_hw_counters.c
> +++ b/drivers/infiniband/sw/rxe/rxe_hw_counters.c
> @@ -37,7 +37,7 @@ int rxe_ib_get_hw_stats(struct ib_device *ibdev,
> return -EINVAL;
>
> for (cnt = 0; cnt < ARRAY_SIZE(rxe_counter_descs); cnt++)
> - stats->value[cnt] = atomic64_read(&dev->stats_counters[cnt]);
> + stats->value[cnt] = rxe_counter_get(dev, cnt);
>
> return ARRAY_SIZE(rxe_counter_descs);
> }
prev parent reply other threads:[~2026-03-29 4:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-29 2:55 [PATCH v2 0/4] Support PERF MGMT for RXE zhenwei pi
2026-03-29 2:55 ` [PATCH v2 1/4] RDMA/rxe: use RXE_PORT instead of magic number 1 zhenwei pi
2026-03-29 2:55 ` [PATCH v2 2/4] RDMA/rxe: add SENT/RCVD bytes zhenwei pi
2026-03-29 2:55 ` [PATCH v2 3/4] RDMA/rxe: support perf mgmt GET method zhenwei pi
2026-03-29 4:54 ` Zhu Yanjun
2026-03-29 2:55 ` [PATCH v2 4/4] RDMA/rxe: use rxe_counter_get zhenwei pi
2026-03-29 4:56 ` Zhu Yanjun [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=3cb474cf-4610-4dc6-b87f-83a9d26122ed@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=zhenwei.pi@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