Nick Piggin wrote:
> #define PG_free 20 /* Page is on the free lists */
> +#define PG_freeing 21 /* PG_refcount about to be freed */
Wow this needs two new page bits. That might be a problem ongoing.
There are only 24 of these puppies and this takes us to just two
remaining. Do we really need _two_ to track free?
One obvious area of overlap might be the PG_nosave_free which seems to
be set on free pages for software suspend. Perhaps that and PG_free
will be equivalent in intent (though maintained differently) and allow
us to recover a bit?
There are a couple of bits which imply ownership such as PG_slab,
PG_swapcache and PG_reserved which to my mind are all exclusive.
Perhaps those plus the PG_free could be combined into a owner field. I
am unsure if the PG_freeing can be 'backed out' if not it may also combine?
Mumble ...
-apw
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
