From: Jason Gunthorpe <jgg@nvidia.com>
To: Sean Hefty <shefty@nvidia.com>
Cc: Michael Margolin <mrgolin@amazon.com>,
"leon@kernel.org" <leon@kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"sleybo@amazon.com" <sleybo@amazon.com>,
"matua@amazon.com" <matua@amazon.com>,
"gal.pressman@linux.dev" <gal.pressman@linux.dev>,
Yonatan Nachum <ynachum@amazon.com>
Subject: Re: [PATCH for-next 1/4] RDMA/core: Add Completion Counters support
Date: Thu, 9 Apr 2026 16:44:20 -0300 [thread overview]
Message-ID: <20260409194420.GT3357077@nvidia.com> (raw)
In-Reply-To: <CH8PR12MB9741DAD52C2D8078B6D366DDBD582@CH8PR12MB9741.namprd12.prod.outlook.com>
On Thu, Apr 09, 2026 at 07:15:31PM +0000, Sean Hefty wrote:
> > > I view this as an implementation option. One vendor may implement
> > > independent counters, which software can then piece together.
> > > However, another implementation may have a tight coupling.
> >
> > Well, this is a problematic state to end up in when deciding the OS and library
> > abstraction. If we don't have joined counters then we can't really support
> > implementations that have tight coupling
> >
> > But if we never see an implementation like that then we wasted our efforts
> > making them combined.
> >
> > It seems like if portals and libfabric defined them as joined together then we
> > probably better support it that way too as someone probably made HW like that.
>
> Can we make this some general counter array, with properties applied
> to the array and no concern with how any specific entry might be
> used (at least from the view of the kernel)?
How does the API work? Who decides where the counter is stored?
Jason
next prev parent reply other threads:[~2026-04-09 19:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 11:54 [PATCH for-next 0/4] Introduce Completion Counters Michael Margolin
2026-04-07 11:54 ` [PATCH for-next 1/4] RDMA/core: Add Completion Counters support Michael Margolin
2026-04-07 14:17 ` Jason Gunthorpe
2026-04-09 16:00 ` Michael Margolin
2026-04-09 16:13 ` Jason Gunthorpe
2026-04-09 17:29 ` Sean Hefty
2026-04-09 18:55 ` Jason Gunthorpe
2026-04-09 19:15 ` Sean Hefty
2026-04-09 19:44 ` Jason Gunthorpe [this message]
2026-04-09 22:23 ` Sean Hefty
2026-04-13 16:14 ` Michael Margolin
2026-04-09 18:36 ` Michael Margolin
2026-04-07 11:54 ` [PATCH for-next 2/4] RDMA/core: Add Completion Counters to resource tracking Michael Margolin
2026-04-07 11:54 ` [PATCH for-next 3/4] RDMA/efa: Update device interface Michael Margolin
2026-04-07 11:54 ` [PATCH for-next 4/4] RDMA/efa: Add Completion Counters support Michael Margolin
2026-04-17 22:41 ` kernel test robot
2026-04-28 22:31 ` [PATCH for-next 0/4] Introduce Completion Counters Doug Ledford
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=20260409194420.GT3357077@nvidia.com \
--to=jgg@nvidia.com \
--cc=gal.pressman@linux.dev \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=matua@amazon.com \
--cc=mrgolin@amazon.com \
--cc=shefty@nvidia.com \
--cc=sleybo@amazon.com \
--cc=ynachum@amazon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.