From: Anand Khoje <anand.a.khoje@oracle.com>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Cc: saeedm@mellanox.com, leon@kernel.org, tariqt@nvidia.com,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
davem@davemloft.net
Subject: Re: [PATCH v5] net/mlx5: Reclaim max 50K pages at once
Date: Tue, 25 Jun 2024 10:30:29 +0530 [thread overview]
Message-ID: <1f9868a7-a336-4a79-bc51-d29461295444@oracle.com> (raw)
In-Reply-To: <0b926745-f2c9-4313-a874-4b7e059b8d64@intel.com>
On 6/25/24 02:11, Jesse Brandeburg wrote:
> On 6/24/2024 8:33 AM, Anand Khoje wrote:
>
>> --- a/drivers/net/ethernet/mellanox/mlx5/core/pagealloc.c
>> +++ b/drivers/net/ethernet/mellanox/mlx5/core/pagealloc.c
>> @@ -608,6 +608,7 @@ enum {
>> RELEASE_ALL_PAGES_MASK = 0x4000,
>> };
>>
>> +#define MAX_RECLAIM_NPAGES -50000
> Can you please explain why this is negative? There doesn't seem to be
> any reason mentioned in the commit message or code.
>
> At the very least it's super confusing to have a MAX be negative, and at
> worst it's a bug. I don't have any other context on this code besides
> this patch, so an explanation would be helpful.
>
>
>
Hi Jesse,
The way Mellanox ConnectX5 driver handles 'release of allocated pages
from HCA' or 'allocation of pages to HCA', is by sending an event to the
host. This event will have number of pages in it. If the number is
positive, that indicates HCA is requesting that number of pages to be
allocated. And if that number is negative, it is the HCA indicating that
that number of pages can be reclaimed by the host.
In this patch we are restricting the maximum number of pages that can be
reclaimed to be 50000 (effectively this would be -50000 as it is
reclaim). This limit is based on the capability of the firmware as it
cannot release more than 50000 back to the host in one go.
I hope that explains.
Thanks,
Anand
next prev parent reply other threads:[~2024-06-25 5:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 15:33 [PATCH v5] net/mlx5: Reclaim max 50K pages at once Anand Khoje
2024-06-24 20:41 ` Jesse Brandeburg
2024-06-25 5:00 ` Anand Khoje [this message]
2024-06-25 20:19 ` Zhu Yanjun
2024-06-26 5:34 ` Leon Romanovsky
2024-06-28 15:44 ` David Laight
2024-07-01 5:39 ` Anand Khoje
2024-07-01 5:40 ` Anand Khoje
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=1f9868a7-a336-4a79-bc51-d29461295444@oracle.com \
--to=anand.a.khoje@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@mellanox.com \
--cc=tariqt@nvidia.com \
/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