Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Gal Pressman <galpress@amazon.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>,
	Doug Ledford <dledford@redhat.com>,
	linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-rc] RDMA/restrack: Track driver QP types in resource tracker
Date: Wed, 31 Jul 2019 13:01:14 +0300	[thread overview]
Message-ID: <20190731100114.GR4878@mtr-leonro.mtl.com> (raw)
In-Reply-To: <08f3d48a-946a-677e-2103-5834ae0238d8@amazon.com>

On Wed, Jul 31, 2019 at 11:51:58AM +0300, Gal Pressman wrote:
> On 31/07/2019 11:34, Leon Romanovsky wrote:
> > On Wed, Jul 31, 2019 at 10:53:10AM +0300, Gal Pressman wrote:
> >> On 31/07/2019 10:46, Leon Romanovsky wrote:
> >>> On Wed, Jul 31, 2019 at 10:05:31AM +0300, Gal Pressman wrote:
> >>>> On 30/07/2019 18:19, Leon Romanovsky wrote:
> >>>>> On Tue, Jul 30, 2019 at 04:49:52PM +0300, Gal Pressman wrote:
> >>>>>> On 30/07/2019 16:38, Leon Romanovsky wrote:
> >>>>>>> On Tue, Jul 30, 2019 at 02:01:37PM +0300, Gal Pressman wrote:
> >>>>>>>> The check for QP type different than XRC has wrongly excluded driver QP
> >>>>>>>> types from the resource tracker.
> >>>>>>>>
> >>>>>>>> Fixes: 78a0cd648a80 ("RDMA/core: Add resource tracking for create and destroy QPs")
> >>>>>>>
> >>>>>>> It is a little bit over to say "wrongly". At that time, we did it on purpose
> >>>>>>> because it was unclear how to represent such QP types to users and we didn't
> >>>>>>> have vendor specific hooks introduced by Steve later on.
> >>>>>>
> >>>>>> It's very confusing to see a test running and zero QPs in "rdma res".
> >>>>>> I'm fine with removing the "wrongly" :), but I still think this should be
> >>>>>> targeted to for-rc as a bug fix.
> >>>>>
> >>>>> Yes, please remove "wrongly" and change Fixes line to be
> >>>>> "Fixes: 40909f664d27 ("RDMA/efa: Add EFA verbs implementation")",
> >>>>> because before addition of EFA driver all other drivers had QPs.
> >>>>
> >>>> How are DC QPs being counted?
> >>>
> >>> They were not counted on purpose. We didn't imagine acceptance of
> >>> non-RDMA driver which doesn't support any standard QPs and doesn't
> >>> work with kernel verbs.
> >>
> >> Running dcping/perftest over DC shows zero QPs?
> >
> > No, try it and you will see other QPs.
> >
> >> On purpose?
> >> Sounds like a bug to me..
> >
> > OK.
>
> Does OK mean you're OK with counting DC QPs after this patch?

I'm OK with the idea, I'm not OK with the description.

Thanks

      reply	other threads:[~2019-07-31 10:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30 11:01 [PATCH for-rc] RDMA/restrack: Track driver QP types in resource tracker Gal Pressman
2019-07-30 12:19 ` Jason Gunthorpe
2019-07-30 12:21   ` Gal Pressman
2019-07-30 13:38 ` Leon Romanovsky
2019-07-30 13:49   ` Gal Pressman
2019-07-30 15:19     ` Leon Romanovsky
2019-07-31  7:05       ` Gal Pressman
2019-07-31  7:46         ` Leon Romanovsky
2019-07-31  7:53           ` Gal Pressman
2019-07-31  8:34             ` Leon Romanovsky
2019-07-31  8:51               ` Gal Pressman
2019-07-31 10:01                 ` Leon Romanovsky [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=20190731100114.GR4878@mtr-leonro.mtl.com \
    --to=leon@kernel.org \
    --cc=dledford@redhat.com \
    --cc=galpress@amazon.com \
    --cc=jgg@ziepe.ca \
    --cc=linux-rdma@vger.kernel.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