From: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
To: Daniel Jurgens <danielj-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Cc: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH rdma-next] IB/core: Only maintain real QPs in the security lists
Date: Tue, 7 Nov 2017 10:32:15 -0700 [thread overview]
Message-ID: <20171107173215.GD7063@ziepe.ca> (raw)
In-Reply-To: <87a902ae-351b-43c4-4a42-b362c981a767-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
On Tue, Nov 07, 2017 at 11:15:12AM -0600, Daniel Jurgens wrote:
> This flow is through ib_modify_qp, it's not user space specific. If
> it really pains you that much it can be changed an inclusive compare
> instead of exclusive.
There was already a RFC on re-purpsing those constants and exposing
them to user space.
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2017-11-07 17:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-07 16:33 [PATCH rdma-next] IB/core: Only maintain real QPs in the security lists Leon Romanovsky
[not found] ` <20171107163326.23881-1-leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2017-11-07 16:46 ` Jason Gunthorpe
2017-11-07 16:52 ` Daniel Jurgens
[not found] ` <065e66ff-e901-bd5c-674d-173eab720989-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-11-07 16:55 ` Jason Gunthorpe
[not found] ` <20171107165539.GB7063-uk2M96/98Pc@public.gmane.org>
2017-11-07 17:10 ` Leon Romanovsky
[not found] ` <20171107171026.GN18825-U/DQcQFIOTAAJjI8aNfphQ@public.gmane.org>
2017-11-07 17:31 ` Jason Gunthorpe
2017-11-07 17:15 ` Daniel Jurgens
[not found] ` <87a902ae-351b-43c4-4a42-b362c981a767-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2017-11-07 17:32 ` Jason Gunthorpe [this message]
2017-11-07 18:40 ` Leon Romanovsky
2017-11-13 21:24 ` 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=20171107173215.GD7063@ziepe.ca \
--to=jgg-uk2m96/98pc@public.gmane.org \
--cc=danielj-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=stable-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).