Driver Verifier- Low memory simulation

NTDEV
1

Hi All,

I was running some tests to check whether my drivers are capable of handling
low memory scenarios the way its expected. I enabled just low memory
simulation on verifier, selected my drivers for verification and rebooted.
After running some I/O tests for around 24 hours, i just checked the
verifier statistics and it shows the number of pool allocations failed as 0.
From what i understand, this should show the number of allocations that was
forcefully failed by verifier. Can some one help me on how to configure the
low memory scenarios ?

Thanks
Anees

2

Anees M wrote:

I was running some tests to check whether my drivers are capable of
handling low memory scenarios the way its expected. I enabled just low
memory simulation on verifier, selected my drivers for verification
and rebooted. After running some I/O tests for around 24 hours, i just
checked the verifier statistics and it shows the number of pool
allocations failed as 0. From what i understand, this should show the
number of allocations that was forcefully failed by verifier. Can some
one help me on how to configure the low memory scenarios ?

Are you actually doing any ExAllocatePool calls? Lots of drivers simply
don’t allocate any memory after initialization. Such a driver is fairly
resiliant in low memory situations. :slight_smile:

–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.

3

Lot of them :-), I also have IO tests running.

On 5/25/05, Tim Roberts wrote:
>
> Anees M wrote:
>
> >
> > I was running some tests to check whether my drivers are capable of
> > handling low memory scenarios the way its expected. I enabled just low
> > memory simulation on verifier, selected my drivers for verification
> > and rebooted. After running some I/O tests for around 24 hours, i just
> > checked the verifier statistics and it shows the number of pool
> > allocations failed as 0. From what i understand, this should show the
> > number of allocations that was forcefully failed by verifier. Can some
> > one help me on how to configure the low memory scenarios ?
> >
>
> Are you actually doing any ExAllocatePool calls? Lots of drivers simply
> don’t allocate any memory after initialization. Such a driver is fairly
> resiliant in low memory situations. :slight_smile:
>
> –
> Tim Roberts, xxxxx@probo.com
> Providenza & Boekelheide, Inc.
>
>
> —
> Questions? First check the Kernel Driver FAQ at
> http://www.osronline.com/article.cfm?id=256
>
> You are currently subscribed to ntdev as: xxxxx@gmail.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>