From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail137.messagelabs.com (mail137.messagelabs.com [216.82.249.19]) by kanga.kvack.org (Postfix) with ESMTP id 546608D0040 for ; Wed, 30 Mar 2011 10:07:12 -0400 (EDT) Received: by qwa26 with SMTP id 26so1145479qwa.14 for ; Wed, 30 Mar 2011 07:07:10 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <1301491622.3283.46.camel@edumazet-laptop> References: <9bde694e1003020554p7c8ff3c2o4ae7cb5d501d1ab9@mail.gmail.com> <1300960540.32158.13.camel@e102109-lin.cambridge.arm.com> <1301395206.583.53.camel@e102109-lin.cambridge.arm.com> <1301399454.583.66.camel@e102109-lin.cambridge.arm.com> <1301476505.29074.47.camel@e102109-lin.cambridge.arm.com> <1301485085.29074.61.camel@e102109-lin.cambridge.arm.com> <1301488032.3283.42.camel@edumazet-laptop> <1301491622.3283.46.camel@edumazet-laptop> Date: Wed, 30 Mar 2011 15:07:09 +0100 Message-ID: Subject: Re: kmemleak for MIPS From: Maxin John Content-Type: text/plain; charset=ISO-8859-1 Sender: owner-linux-mm@kvack.org List-ID: To: Eric Dumazet Cc: Daniel Baluta , Catalin Marinas , naveen yadav , linux-mips@linux-mips.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org Hi Eric, > Hmm, then MIPS kmemleak port might have a problem with percpu data ? > > fcp->hash_table = kzalloc_node(sz, GFP_KERNEL, cpu_to_node(cpu)); > > fcp is a per cpu "struct flow_cache_percpu" Thank you very much for the inputs. I will definitely investigate this. However, I think, the "basic" kmemleak support for MIPS is working as expected with the present patch. The kmemleak test case is also working as expected in MIPS target. So, as Daniel mentioned, shall we go ahead with integrating the kmemleak support for MIPS ? Please let me know your comments. Cheers, Maxin -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org