public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
Cc: Alex Margolin <alexma-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [RFC] Vendor-specific QPs
Date: Sun, 5 Nov 2017 09:25:00 +0200	[thread overview]
Message-ID: <20171105072500.GE31774@mtr-leonro.local> (raw)
In-Reply-To: <20171102200158.GU18874-uk2M96/98Pc@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]

On Thu, Nov 02, 2017 at 02:01:58PM -0600, Jason Gunthorpe wrote:
> On Mon, Oct 30, 2017 at 03:23:24PM +0000, Alex Margolin wrote:
>
> > We propose using the "reserved" range of QP types to serve the
> > vendor-specific implementation, both within the Verbs API (API patch
> > below) and the IB subsystem (ib_core). The solution requires minor
> > changes to IB core, namely removing some restrictions that apply to
> > standard QPs at creation, but most of the flow (and the one for
> > modify and destroy) remains identical.
>
> > The changes to support such QPs will remain in the vendor-specific
> > area of the API, i.e. Mellanox "Direct Verbs" portion, and the
> > change in ib_core is to use specific IB_QPT_RESERVED* definitions to
> > cut through some of the required checks (but still using most of the
> > logic, where applicable). No change to libibverbs is required.
>
> Don't like the idea of a generic RESERVED.
>
> Add a type called IB_QPT_DIRECT_VERBS and put any other information

+1
If we go in this route, it will be much easier for me to present QP types.

root@mtr-leonro:~# /mnt/iproute2/rdma/rdma res show qp dev mlx5_1
QPN	DEV	USER/KERNEL	TYPE	STATE	PID	COMM
8	mlx5_1	USER		UD	RESET	1	rdma
7	mlx5_1	USER		UD	RTS	1	rdma
1	mlx5_1	USER		GSI	RTS	1	rdma
1	mlx5_1	USER		GSI	RTS	1	rdma
0	mlx5_1	USER		SMI	RTS	1	rdma

Thanks

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2017-11-05  7:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-30 15:23 [RFC] Vendor-specific QPs Alex Margolin
     [not found] ` <VI1PR05MB12784029D1DE2689A8194A58B9590-79XLn2atqDMOK6E67s+DINqRiQSDpxhJvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-11-02 20:01   ` Jason Gunthorpe
     [not found]     ` <20171102200158.GU18874-uk2M96/98Pc@public.gmane.org>
2017-11-05  7:25       ` Leon Romanovsky [this message]
2017-11-22 17:47       ` Alex Margolin
     [not found]         ` <VI1PR05MB1278EA7700D1BEB63383FC52B9200-79XLn2atqDMOK6E67s+DINqRiQSDpxhJvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2017-11-22 18:07           ` Jason Gunthorpe
     [not found]             ` <20171122180731.GS18272-uk2M96/98Pc@public.gmane.org>
2017-11-22 20:09               ` Alex Margolin
2017-11-23  9:14               ` Moni Shoua
     [not found]                 ` <CAG9sBKPqVwbS0cXQPTdWCx7vwWaq5EMeghnPMEHrMZZsSsEu_g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-23 17:57                   ` Jason Gunthorpe

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=20171105072500.GE31774@mtr-leonro.local \
    --to=leon-dgejt+ai2ygdnm+yrofe0a@public.gmane.org \
    --cc=alexma-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
    --cc=jgg-uk2M96/98Pc@public.gmane.org \
    --cc=linux-rdma-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