I have a windows device driver that allocates kernel memory from paged
pool (ExAllocatePoolWithTag).

One of the issues I face is how to determine how much kernel paged
pool memory I can allocate without putting memory pressure on the
system (win2k, 2003, etc)

What I'd like to be able to determine at driver initialization is how
much paged pool is currently being used system-wide, and what the
total paged pool size is.
I can figure out how to optimize later.

If this isnt possible you can still receive credit if you provide some
evidence of why not. If it is possible, of course a few lines of code
would be appreciated.