Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932157AbdIRQVk (ORCPT ); Mon, 18 Sep 2017 12:21:40 -0400 Received: from bombadil.infradead.org ([65.50.211.133]:47822 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756040AbdIRQVj (ORCPT ); Mon, 18 Sep 2017 12:21:39 -0400 Date: Mon, 18 Sep 2017 09:21:35 -0700 From: Christoph Hellwig To: Shivasharan Srikanteshwara Cc: Christoph Hellwig , shuwang@redhat.com, Kashyap Desai , Sumit Saxena , jejb@linux.vnet.ibm.com, martin.petersen@oracle.com, "PDL,MEGARAIDLINUX" , linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org, chuhu@redhat.com, yizhan@redhat.com, catalin.marinas@arm.com Subject: Re: [PATCH V2] megaraid: kmemleak: Track page allocation for fusion Message-ID: <20170918162135.GA20366@infradead.org> References: <20170915052152.5032-1-shuwang@redhat.com> <20170915180007.GA24045@infradead.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.3 (2017-05-23) X-SRS-Rewrite: SMTP reverse-path rewritten from by bombadil.infradead.org. See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 218 Lines: 5 Oh, I missed log_to_span. Well, in that case log_to_span is _the_ candidate for moving into a separate allocation. And in fact you're probably better off by using a sensible data structure for it, e.g. a radix tree.