A little plea for mercy for this tiny bit :)
Could we keep PG_slab around unless its really causing trouble ? It
makes life easier for some things we do ... Also its rather nice that
today as a result of a wide usage of
slab infrastructure in the kernel, one can easily/directly interpret the
contents of
almost any arbitrary memory location in the kernel, if its a slab page,
as one knows what type of data it contains.
> +#define PG_skip 10 /* kill me now: obsolete */
> #define PG_highmem 11
> #define PG_checked 12 /* kill me in 2.5.<early>. */
> #define PG_arch_1 13
> #define PG_reserved 14
> #define PG_launder 15 /* written out by VM pressure.. */
> -
> #define PG_private 16 /* Has something at ->private */
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/