From: Jason Gunthorpe <jgg@nvidia.com>
To: Bernard Metzler <BMT@zurich.ibm.com>
Cc: Bob Pearson <rpearsonhpe@gmail.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: Re: another change breaks rxe
Date: Fri, 30 Oct 2020 13:28:05 -0300 [thread overview]
Message-ID: <20201030162805.GE2620339@nvidia.com> (raw)
In-Reply-To: <OFAB5249F6.49569DF7-ON00258611.0045601D-00258611.00467F48@notes.na.collabserv.com>
On Fri, Oct 30, 2020 at 12:50:01PM +0000, Bernard Metzler wrote:
> I see the hfi and ipath drivers similarly using ibv_cmd_post_send
> to push the wqe's (while not having them in shared mem). Do they
> brake as well?
> Do we have an example of decent eventfd usage where I could learn
> from how to use it?
You'd add a uAPI accepting a eventfd and then call a sequence like:
init_waitqueue_func_entry(.., my_func);
init_poll_funcptr(..);
events = vfs_poll(evfile, ..);
And my_func will be called when the user does write() on the event fd.
drivers/vfio/virqfd.c has the simplest version of this
It could be some core code to do this setup with a new driver callback
'user_doorbell_trigger' or something like that.
However, I see at closer inspection that rxe and siw both want the QPN
to be passed in, so this doesn't look like it would work - an eventfd
per QP is too much overhead.
But calling post_send, even with a 0 length, is really slow.
Jason
prev parent reply other threads:[~2020-10-30 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 5:41 another change breaks rxe Bob Pearson
2020-10-30 11:47 ` Jason Gunthorpe
2020-10-30 12:50 ` Bernard Metzler
2020-10-30 16:28 ` Jason Gunthorpe [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=20201030162805.GE2620339@nvidia.com \
--to=jgg@nvidia.com \
--cc=BMT@zurich.ibm.com \
--cc=linux-rdma@vger.kernel.org \
--cc=rpearsonhpe@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