Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Doug Ledford <dledford@redhat.com>,
	Gal Pressman <galpress@amazon.com>,
	linux-rdma@vger.kernel.org
Subject: Re: [PATCH rdma-next v1 07/13] RDMA/core: Allow drivers to disable restrack DB
Date: Sun, 6 Sep 2020 17:25:40 +0300	[thread overview]
Message-ID: <20200906142540.GH55261@unreal> (raw)
In-Reply-To: <20200903140202.GA1552016@nvidia.com>

On Thu, Sep 03, 2020 at 11:02:02AM -0300, Jason Gunthorpe wrote:
> On Sun, Aug 30, 2020 at 01:14:30PM +0300, Leon Romanovsky wrote:
> > diff --git a/include/rdma/restrack.h b/include/rdma/restrack.h
> > index 10bfed0fcd32..d52f7ad6641f 100644
> > +++ b/include/rdma/restrack.h
> > @@ -68,6 +68,14 @@ struct rdma_restrack_entry {
> >  	 * As an example for that, see mlx5 QPs with type MLX5_IB_QPT_HW_GSI
> >  	 */
> >  	bool			valid;
> > +	/**
> > +	 * @no_track: don't add this entry to restrack DB
> > +	 *
> > +	 * This field is used to mark an entry that doesn't need to be added to
> > +	 * internal restrack DB and presented later to the users at the nldev
> > +	 * query stage.
> > +	 */
> > +	u8			no_track : 1;
> >  	/*
> >  	 * @kref: Protect destroy of the resource
> >  	 */
>
> The valid may as well be changed to a bitfield too

I will delete "valid" later in this series.

>
>
> > +/**
> > + * rdma_restrack_no_track() - don't add resource to the DB
> > + * @res: resource entry
> > + *
> > + * Every user of thie API should be cross examined.
> > + * Probaby you don't need to use this function.
> > + */
> > +static inline void rdma_restrack_no_track(struct rdma_restrack_entry *res)
> > +{
> > +	res->no_track = true;
> > +}
> > +static inline bool rdma_restrack_is_tracked(struct rdma_restrack_entry *res)
> > +{
> > +	return !res->no_track;
> > +}
>
> Are these wrappers really necessary?

I don't like them either, added them to make same interface for all
restrack operations.

>
> Jason

  reply	other threads:[~2020-09-06 14:26 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-30 10:14 [PATCH rdma-next v1 00/13] Track memory allocation with restrack DB help Leon Romanovsky
2020-08-30 10:14 ` [PATCH rdma-next v1 01/13] RDMA/cma: Delete from restrack DB after successful destroy Leon Romanovsky
2020-09-03 14:27   ` Jason Gunthorpe
2020-09-06 14:28     ` Leon Romanovsky
2020-08-30 10:14 ` [PATCH rdma-next v1 02/13] RDMA/mlx5: Don't call to restrack recursively Leon Romanovsky
2020-08-30 10:14 ` [PATCH rdma-next v1 03/13] RDMA/restrack: Count references to the verbs objects Leon Romanovsky
2020-08-30 10:14 ` [PATCH rdma-next v1 04/13] RDMA/restrack: Simplify restrack tracking in kernel flows Leon Romanovsky
2020-08-30 10:14 ` [PATCH rdma-next v1 05/13] RDMA/restrack: Improve readability in task name management Leon Romanovsky
2020-08-30 10:14 ` [PATCH rdma-next v1 06/13] RDMA/cma: Be strict with attaching to CMA device Leon Romanovsky
2020-08-30 10:14 ` [PATCH rdma-next v1 07/13] RDMA/core: Allow drivers to disable restrack DB Leon Romanovsky
2020-09-03 14:02   ` Jason Gunthorpe
2020-09-06 14:25     ` Leon Romanovsky [this message]
2020-08-30 10:14 ` [PATCH rdma-next v1 08/13] RDMA/counter: Combine allocation and bind logic Leon Romanovsky
2020-08-30 10:14 ` [PATCH rdma-next v1 09/13] RDMA/restrack: Store all special QPs in restrack DB Leon Romanovsky
2020-08-30 10:14 ` [PATCH rdma-next v1 10/13] RDMA/restrack: Make restrack DB mandatory for IB objects Leon Romanovsky
2020-08-30 10:14 ` [PATCH rdma-next v1 11/13] RDMA/restrack: Support all QP types Leon Romanovsky
2020-08-30 10:14 ` [PATCH rdma-next v1 12/13] RDMA/core: Track device memory MRs Leon Romanovsky
2020-08-30 10:14 ` [PATCH rdma-next v1 13/13] RDMA/restrack: Drop valid restrack field as source of ambiguity Leon Romanovsky
2020-09-03 16:21   ` Jason Gunthorpe
2020-09-06 14:24     ` Leon Romanovsky
2020-09-06 14:28       ` Jason Gunthorpe
2020-09-06 15:24         ` Leon Romanovsky

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=20200906142540.GH55261@unreal \
    --to=leon@kernel.org \
    --cc=dledford@redhat.com \
    --cc=galpress@amazon.com \
    --cc=jgg@nvidia.com \
    --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