[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180918144623.GI11367@ziepe.ca>
Date: Tue, 18 Sep 2018 08:46:23 -0600
From: Jason Gunthorpe <jgg@...pe.ca>
To: Jan Dakinevich <jan.dakinevich@...tuozzo.com>
Cc: Doug Ledford <dledford@...hat.com>,
Yishai Hadas <yishaih@...lanox.com>,
Leon Romanovsky <leon@...nel.org>,
Parav Pandit <parav@...lanox.com>,
Mark Bloch <markb@...lanox.com>,
Daniel Jurgens <danielj@...lanox.com>,
Kees Cook <keescook@...omium.org>,
Kamal Heib <kamalheib1@...il.com>,
Bart Van Assche <bvanassche@....org>,
linux-rdma@...r.kernel.org, linux-kernel@...r.kernel.org,
Denis Lunev <den@...tuozzo.com>,
Konstantin Khorenko <khorenko@...tuozzo.com>
Subject: Re: [PATCH 0/4] IB: decrease large contigous allocation
On Tue, Sep 18, 2018 at 04:03:42PM +0300, Jan Dakinevich wrote:
> The size of mlx4_ib_device became too large to be allocated as whole contigous
> block of memory. Currently it takes about 55K. On architecture with 4K page it
> means 3rd order.
>
> This patch series makes an attempt to split mlx4_ib_device into several parts
> and allocate them with less expensive kvzalloc
Why split it up? Any reason not to just allocate the whole thing with
kvzalloc?
Jason
Powered by blists - more mailing lists