Subject: Re: kern/13232: POOL_DIAGNOSTIC && pool.h
To: Rafal Boni <firstname.lastname@example.org>
From: Assar Westerlund <email@example.com>
Date: 06/19/2001 18:08:36
Rafal Boni <firstname.lastname@example.org> writes:
> This makes *everyone* pay the
> price (even in totally production-tuned configurations), and as such
> seems wrong-headed.
It used to be that without POOL_DIAGNOSTIC you directly called
pool_get, pool_put, and pool_reclaim. With POOL_DIAGNOSTIC, macros
were added that sent in __FILE__ and __LINE__ as separate parameters
to the functions (now with an underscore in front). My patch made
that always be the case. If POOL_DIAGNOSTIC is not defined, these
just get ignored. This will keep the API the same, and hide the fact
that diagnostic checks are (or not) performed.