All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: 康宁 <kangning18z@ict.ac.cn>
Cc: haakon.bugge@oracle.com, linux-rdma@vger.kernel.org
Subject: Re: Re: [PATCH v3] Fix one error in mthca_alloc
Date: Tue, 31 Aug 2021 15:00:07 +0300	[thread overview]
Message-ID: <YS4Zx30hAa9FuL5E@unreal> (raw)
In-Reply-To: <30f8792b.1e35e.17b9bcbf058.Coremail.kangning18z@ict.ac.cn>

On Tue, Aug 31, 2021 at 06:40:38PM +0800, 康宁 wrote:
> &gt; 
> &gt; On Fri, Aug 27, 2021 at 08:52:28AM +0800, kangning wrote:
> &gt; &gt; drivers/infiniband/hw/mthca/mthca_allocator.c: alloc-&gt;last left unchanged in mthca_alloc, which
> &gt; &gt; has impact on performance of function find_next_zero_bit in mthca_alloc.
> &gt; 
> &gt; I don't know what the sentence above means, but the change is unlikely
> &gt; to be correct.
> &gt; 
> &gt; When alloc-&gt;last starts to be equal to alloc-&gt;max, the
> &gt; find_next_zero_bit() will always return alloc-&gt;max. which will ensure
> &gt; that the following code is executed.
> &gt; 
> &gt;    48         if (obj &gt;= alloc-&gt;max) {
> &gt;    49                 alloc-&gt;top = (alloc-&gt;top + alloc-&gt;max) &amp; alloc-&gt;mask;
> &gt;    50                 obj = find_first_zero_bit(alloc-&gt;table, alloc-&gt;max);
> &gt;    51         }
> &gt; 
> 
> Thanks for your review.
> Yes, your analysis is right. However, this is a bitmap allocator for resource id allocation (like QP, and CQ). 
> We first look at the situation where no resource id is released.
> When the value of alloc-&gt;last starts to reaches alloc-&gt;max, the bitmap will 
> be full. In this case, it's normal to return an invalid value.
> 
> Now, let's add resource releasing into consideration. 
> The following code is part of mthca_free:
> 
> 70	spin_lock_irqsave(&amp;alloc-&gt;lock, flags);
> 71
> 72	clear_bit(obj, alloc-&gt;table);
> 73	alloc-&gt;last = min(alloc-&gt;last, obj);
> 74	alloc-&gt;top = (alloc-&gt;top + alloc-&gt;max) &amp; alloc-&gt;mask;
> 
> mthca_free() is used to release the allocated resource id. It will update alloc-&gt;last when obj is freed. 
> So, if the bitmap has space for allocation, my modification can continuously work.

After alloc->last starts to be equal to alloc->max, the bitmap is
searches with find_first_zero_bit() call. That will ensure that we look
for any bit between 0 and alloc->max.

So no, your change can't be right.

Thanks

> 
> &gt; 
> &gt; However the mthca_alloc() function has other error, it returns -1 while
> &gt; based on its declaration it needs to be unsigned,
> 
> I think you are right about this. But obj is the return value of u32 type, which is the requirement of resource id 
> (though it may not fully use 32 bits). I have no idea of how to fix it.
> 
> Thanks.
> 
> &gt; 
> &gt; Thanks
> &gt; 
> &gt; &gt; 
> &gt; &gt; Signed-off-by: kangning <kangning18z@ict.ac.cn>
> &gt; &gt; ---
> &gt; &gt;  
> &gt; &gt;  I squashed two commits into one in this version.
> &gt; &gt;  
> &gt; &gt;  drivers/infiniband/hw/mthca/mthca_allocator.c | 3 +++
> &gt; &gt;  1 file changed, 3 insertions(+)
> &gt; &gt; 
> &gt; &gt; diff --git a/drivers/infiniband/hw/mthca/mthca_allocator.c b/drivers/infiniband/hw/mthca/mthca_allocator.c
> &gt; &gt; index aef1d274a14e..1141695093e7 100644
> &gt; &gt; --- a/drivers/infiniband/hw/mthca/mthca_allocator.c
> &gt; &gt; +++ b/drivers/infiniband/hw/mthca/mthca_allocator.c
> &gt; &gt; @@ -51,6 +51,9 @@ u32 mthca_alloc(struct mthca_alloc *alloc)
> &gt; &gt;  	}
> &gt; &gt;  
> &gt; &gt;  	if (obj &lt; alloc-&gt;max) {
> &gt; &gt; +		alloc-&gt;last = obj + 1;
> &gt; &gt; +		if (alloc-&gt;last == alloc-&gt;max)
> &gt; &gt; +			alloc-&gt;last = 0;
> &gt; &gt;  		set_bit(obj, alloc-&gt;table);
> &gt; &gt;  		obj |= alloc-&gt;top;
> &gt; &gt;  	} else
> &gt; &gt; -- 
> &gt; &gt; 2.17.1
> &gt; &gt; 
> </kangning18z@ict.ac.cn>

  reply	other threads:[~2021-08-31 12:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-27  0:52 [PATCH v3] Fix one error in mthca_alloc kangning
2021-08-31  9:52 ` Leon Romanovsky
2021-08-31 10:40   ` 康宁
2021-08-31 12:00     ` Leon Romanovsky [this message]
2021-08-31 12:16       ` kangning18z
2021-08-31 10:47   ` 康宁
     [not found]   ` <202109011027459851120@ict.ac.cn>
2021-09-01  7:51     ` 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=YS4Zx30hAa9FuL5E@unreal \
    --to=leon@kernel.org \
    --cc=haakon.bugge@oracle.com \
    --cc=kangning18z@ict.ac.cn \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.