On Wed, 23 May 2007 20:00:52 -0700 (PDT) Christoph Lameter wrote: > New version with Randy's fixes:
well... :) > Index: slub/Documentation/kernel-parameters.txt > =================================================================== > --- slub.orig/Documentation/kernel-parameters.txt 2007-05-23 > 19:34:49.000000000 -0700 > +++ slub/Documentation/kernel-parameters.txt 2007-05-23 19:58:04.000000000 > -0700 > @@ -1589,6 +1589,37 @@ and is between 256 and 4096 characters. > > slram= [HW,MTD] > > + slub_debug [MM, SLUB] > + Enabling slub_debug allows to determine the culprit allows ___(who)____ > + if slab objects become corrupted. Enabling slub_debug > + creates guard zones around objects and poisons objects > + when not in use. Also tracks the last alloc / free. > + For more information see Documentation/vm/slub.txt. > + > + slub_min_order= [MM, SLUB] > + Determines the mininum page order for slabs. Must be > + lower than slub_max_order ^. (end with period) > + For more information see Documentation/vm/slub.txt. > Index: slub/Documentation/vm/slub.txt > =================================================================== > --- slub.orig/Documentation/vm/slub.txt 2007-05-23 19:34:49.000000000 > -0700 > +++ slub/Documentation/vm/slub.txt 2007-05-23 19:59:45.000000000 -0700 > +Slab validation > +--------------- > + > +SLUB can validate all object if the kernel was booted with slub_debug. In > +order to do so you must have the slabinfo tool. Then you can do > + > +slabinfo -v > + > +which will test all objects. Output will be generated to the syslog. > + > +This also works in a more limited way if boot was without slab debug. > +In that case slabinfo -v simply tests all reachable objects. Usually > +these are in the cpu slabs and the partial slabs. Full slabs are not CPU > +tracked by SLUB in a non debug situation. --- ~Randy *** Remember to use Documentation/SubmitChecklist when testing your code *** - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/