Re: [PATCH v2] IB/mlx5: Reduce max order of memory allocated for xlt update

From: Jason Gunthorpe <jgg@ziepe.ca>
To: Aruna Ramakrishna <aruna.ramakrishna@oracle.com>
Cc: Praveen Kumar Kannoju <praveen.kannoju@oracle.com>,
	leon@kernel.org, dledford@redhat.com, linux-rdma@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Rajesh Sivaramasubramaniom 
	<rajesh.sivaramasubramaniom@oracle.com>,
	Rama Nichanamatlu <rama.nichanamatlu@oracle.com>,
	Jeffery Yoder <jeffery.yoder@oracle.com>
Subject: Re: [PATCH v2] IB/mlx5: Reduce max order of memory allocated for xlt update
Date: Tue, 23 Mar 2021 20:13:21 -0300	[thread overview]
Message-ID: <20210323231321.GF2710221@ziepe.ca> (raw)
In-Reply-To: <80966C8E-341B-4F5D-9DCA-C7D82AB084D5@oracle.com>

On Tue, Mar 23, 2021 at 12:41:51PM -0700, Aruna Ramakrishna wrote:
>    There is a far greater possibility of an order-8 allocation failing,
>    esp. with the addition of __GFP_NORETRY , and the code would have to
>    fall back to a lower order allocation more often than not (esp. on a
>    long running system). Unless the performance gains from using order-8
>    pages is significant (and it does not seem that way to me), we can just
>    skip this step and directly go to the lower order allocation.

Do not send HTML mails.

Do you have benchmarks that show the performance of the high order
pages is not relavent? I'm a bit surprised to hear that

This code really needs some attention to use a proper
scatter/gather. I understand the chip can do it, just some of the
software layers need to be stripped away so it can form the right SGL
in the HW.

Jason