netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: David Laight <David.Laight@aculab.com>
Cc: Anand Khoje <anand.a.khoje@oracle.com>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"saeedm@mellanox.com" <saeedm@mellanox.com>,
	"tariqt@nvidia.com" <tariqt@nvidia.com>,
	"edumazet@google.com" <edumazet@google.com>,
	"kuba@kernel.org" <kuba@kernel.org>,
	"pabeni@redhat.com" <pabeni@redhat.com>,
	"davem@davemloft.net" <davem@davemloft.net>
Subject: Re: [PATCH v4] net/mlx5: Reclaim max 50K pages at once
Date: Mon, 1 Jul 2024 14:49:49 +0300	[thread overview]
Message-ID: <20240701114949.GB13195@unreal> (raw)
In-Reply-To: <3d5b16d332914d4f810bc0ce48fd8772@AcuMS.aculab.com>

On Fri, Jun 28, 2024 at 03:13:45PM +0000, David Laight wrote:
> From: Leon Romanovsky
> > Sent: 24 June 2024 10:58
> > 
> > On Wed, Jun 19, 2024 at 06:58:27PM +0530, Anand Khoje wrote:
> > > In non FLR context, at times CX-5 requests release of ~8 million FW pages.
> > > This needs humongous number of cmd mailboxes, which to be released once
> > > the pages are reclaimed. Release of humongous number of cmd mailboxes is
> > > consuming cpu time running into many seconds. Which with non preemptible
> > > kernels is leading to critical process starving on that cpu’s RQ.
> > > To alleviate this, this change restricts the total number of pages
> > > a worker will try to reclaim maximum 50K pages in one go.
> > > The limit 50K is aligned with the current firmware capacity/limit of
> > > releasing 50K pages at once per MLX5_CMD_OP_MANAGE_PAGES + MLX5_PAGES_TAKE
> > > device command.
> > >
> > > Our tests have shown significant benefit of this change in terms of
> > > time consumed by dma_pool_free().
> > > During a test where an event was raised by HCA
> > > to release 1.3 Million pages, following observations were made:
> > >
> > > - Without this change:
> > > Number of mailbox messages allocated was around 20K, to accommodate
> > > the DMA addresses of 1.3 million pages.
> > > The average time spent by dma_pool_free() to free the DMA pool is between
> > > 16 usec to 32 usec.
> > >            value  ------------- Distribution ------------- count
> > >              256 |                                         0
> > >              512 |@                                        287
> > >             1024 |@@@                                      1332
> > >             2048 |@                                        656
> > >             4096 |@@@@@                                    2599
> > >             8192 |@@@@@@@@@@                               4755
> > >            16384 |@@@@@@@@@@@@@@@                          7545
> > >            32768 |@@@@@                                    2501
> > >            65536 |                                         0
> > >
> > > - With this change:
> > > Number of mailbox messages allocated was around 800; this was to
> > > accommodate DMA addresses of only 50K pages.
> > > The average time spent by dma_pool_free() to free the DMA pool in this case
> > > lies between 1 usec to 2 usec.
> > >            value  ------------- Distribution ------------- count
> > >              256 |                                         0
> > >              512 |@@@@@@@@@@@@@@@@@@                       346
> > >             1024 |@@@@@@@@@@@@@@@@@@@@@@                   435
> > >             2048 |                                         0
> > >             4096 |                                         0
> > >             8192 |                                         1
> > >            16384 |                                         0
> > >
> > > Signed-off-by: Anand Khoje <anand.a.khoje@oracle.com>
> > > Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
> > > ---
> > > Changes in v4:
> > >   - Fixed a nit in patch subject.
> > > ---
> > >  drivers/net/ethernet/mellanox/mlx5/core/pagealloc.c | 7 ++++++-
> > >  1 file changed, 6 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/net/ethernet/mellanox/mlx5/core/pagealloc.c
> > b/drivers/net/ethernet/mellanox/mlx5/core/pagealloc.c
> > > index dcf58ef..06eee3a 100644
> > > --- 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
> 
> It would be traditional to enclose a negative value in ().
> (Although only 30+ year old compilers would generate unexpected code for
> 	foo-MAX_RECLAIM_NPAGES
> and you have to go back into the 1970s for
> 	foo=MAX_RECLAIM_NPAGES
> to be a problem.)
> 
> > >  static int req_pages_handler(struct notifier_block *nb,
> > >  			     unsigned long type, void *data)
> > >  {
> > > @@ -639,9 +640,13 @@ static int req_pages_handler(struct notifier_block *nb,
> > >
> > >  	req->dev = dev;
> > >  	req->func_id = func_id;
> > > -	req->npages = npages;
> > >  	req->ec_function = ec_function;
> > >  	req->release_all = release_all;
> > > +	if (npages < MAX_RECLAIM_NPAGES)
> > > +		req->npages = MAX_RECLAIM_NPAGES;
> > > +	else
> > > +		req->npages = npages;
> > > +
> > 
> > BTW, this can be written as:
> > 	req->npages = max_t(s32, npages, MAX_RECLAIM_NPAGES);
> 
> That shouldn't need all the (s32) casts.

#define doesn't have a type, so it is better to be explicit here.

> (I don't think it even needed them before I relaxed the type check.)
> 
> 	David
> 
> > 
> > Thanks
> > 
> > >  	INIT_WORK(&req->work, pages_work_handler);
> > >  	queue_work(dev->priv.pg_wq, &req->work);
> > >  	return NOTIFY_OK;
> > > --
> > > 1.8.3.1
> > >
> 
> -
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
> Registration No: 1397386 (Wales)

  reply	other threads:[~2024-07-01 11:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 13:28 [PATCH v4] net/mlx5: Reclaim max 50K pages at once Anand Khoje
2024-06-24  9:57 ` Leon Romanovsky
2024-06-24 15:48   ` Anand Khoje
2024-06-28 15:13   ` David Laight
2024-07-01 11:49     ` Leon Romanovsky [this message]
2024-07-15  8:22       ` David Laight
2024-07-15 10:23         ` 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=20240701114949.GB13195@unreal \
    --to=leon@kernel.org \
    --cc=David.Laight@aculab.com \
    --cc=anand.a.khoje@oracle.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@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;
as well as URLs for NNTP newsgroup(s).