From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Lameter Subject: Re: [Bug #13319] Page allocation failures with b43 and p54usb Date: Tue, 30 Jun 2009 18:18:24 -0400 (EDT) Message-ID: References: <5Hhc7UkUKEO.A.fNH.4kASKB@chimera> <4A48F114.1010702@lwfinger.net> <84144f020906292355o7cf63f7ch47bd19961cf92da3@mail.gmail.com> <1246374095.8014.28.camel@penberg-laptop> Mime-Version: 1.0 Return-path: In-Reply-To: Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: TEXT/PLAIN; charset="us-ascii" Content-Transfer-Encoding: 7bit To: David Rientjes Cc: Pekka Enberg , Larry Finger , "Rafael J. Wysocki" , Linux Kernel Mailing List , Kernel Testers List , Johannes Berg On Tue, 30 Jun 2009, David Rientjes wrote: > I'm curious whether there would ever be any use for disabling debugging on > specific caches for reasons other than higher minimum orders for metadata, > though, given that we already support things like slub_debug=FZ,cache, > which should only enable free debugging and redzoning even with > CONFIG_SLUB_DEBUG_ON enabled for cache. One of the reasons for disabling debugging is to speed up the kernel. Race conditions may vanish due to the additional latency added by the debugging code. Ideally you know which slab cache has the race and you only would enable it on that one.