From: Jason Gunthorpe <jgg@nvidia.com>
To: Michael Margolin <mrgolin@amazon.com>
Cc: leon@kernel.org, linux-rdma@vger.kernel.org, sleybo@amazon.com,
matua@amazon.com, 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 13:13:57 -0300 [thread overview]
Message-ID: <20260409161357.GL3357077@nvidia.com> (raw)
In-Reply-To: <20260409160007.GA24340@dev-dsk-mrgolin-1c-b2091117.eu-west-1.amazon.com>
On Thu, Apr 09, 2026 at 04:00:07PM +0000, Michael Margolin wrote:
> EFA actually has a single counter object type that can count all events
> as you suggest here, but I chose to define a single container for
> success and error completion counts in core for three main reasons:
>
> 1. Consistency with userspace - we usually have a 1:1 mapping between
> rdma-core and kernel objects.
Well here we would have two kernel objects right?
> 2. Although the UE spec does not define HW interfaces, it does couple
> success and error counting.
It's just counting, it seem slike the api is you get a counter and
when certain events happen it counts. You get to pick what incrs that
counter.
> 3. A single object for success and error completions gives more freedom
> to device implementations. For instance, it allows optimizing device
> HW resources by implementing the error counter in a less performant
> way.
This can be done anyhow by choosing fast/slow counters based on the
requested bits to count. If userspace requests an error only counter
it can be routed properly.
Jason
next prev parent reply other threads:[~2026-04-09 16:14 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 [this message]
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
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=20260409161357.GL3357077@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=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.