Allocate a large buffer for Virtual Disk

I’m using the Microsoft RAM Disk Driver for Windows 2000. In my system are
384MB RAM, but when i set the RAM Disk Size to 128MB the driver failed to
allocate the memory. The driver uses ExAllocatePool(NonPagedPool,…). I
think the problem is the memory fragmentation (say me if i’m wrong). Any
suggestions ?

A. Roth


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

I would suggest you allocate the memory from the paged pool instead of using
non-paged memory for the ramdisk driver. I think the reason it won’t
allocate that much non-paged memory is because it is a limited resource.
Instead use MmProbeAndLockPages() to keep your memory resident.

Brian

----- Original Message -----
From: “Andreas Roth”
To: “NT Developers Interest List”
Sent: Thursday, June 07, 2001 11:08 AM
Subject: [ntdev] Allocate a large buffer for Virtual Disk

> I’m using the Microsoft RAM Disk Driver for Windows 2000. In my system are
> 384MB RAM, but when i set the RAM Disk Size to 128MB the driver failed to
> allocate the memory. The driver uses ExAllocatePool(NonPagedPool,…). I
> think the problem is the memory fragmentation (say me if i’m wrong). Any
> suggestions ?
>
> A. Roth
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@sginet.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

That’s right. But when i use paged memory i can use a physical storage. Than
the system can put the entire virtual disk to a pagefile. I want to have the
most possible performance!

A. Roth

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Brian Palmer
Sent: Freitag, 8. Juni 2001 04:00
To: NT Developers Interest List
Subject: [ntdev] Re: Allocate a large buffer for Virtual Disk

I would suggest you allocate the memory from the paged pool instead of using
non-paged memory for the ramdisk driver. I think the reason it won’t
allocate that much non-paged memory is because it is a limited resource.
Instead use MmProbeAndLockPages() to keep your memory resident.

Brian

----- Original Message -----
From: “Andreas Roth”
To: “NT Developers Interest List”
Sent: Thursday, June 07, 2001 11:08 AM
Subject: [ntdev] Allocate a large buffer for Virtual Disk

> I’m using the Microsoft RAM Disk Driver for Windows 2000. In my system are
> 384MB RAM, but when i set the RAM Disk Size to 128MB the driver failed to
> allocate the memory. The driver uses ExAllocatePool(NonPagedPool,…). I
> think the problem is the memory fragmentation (say me if i’m wrong). Any
> suggestions ?
>
> A. Roth
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@sginet.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>


You are currently subscribed to ntdev as: xxxxx@arsoft-online.de
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Thats why you setup a MDL and call MmProbeAndLockPages() on it. That will
prevent windows from paging them out to disk.

Brian

----- Original Message -----
From: “Andreas Roth”
To: “NT Developers Interest List”
Sent: Friday, June 08, 2001 12:30 AM
Subject: [ntdev] Re: Allocate a large buffer for Virtual Disk

> That’s right. But when i use paged memory i can use a physical storage.
Than
> the system can put the entire virtual disk to a pagefile. I want to have
the
> most possible performance!
>
> A. Roth
>
> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Brian Palmer
> Sent: Freitag, 8. Juni 2001 04:00
> To: NT Developers Interest List
> Subject: [ntdev] Re: Allocate a large buffer for Virtual Disk
>
>
> I would suggest you allocate the memory from the paged pool instead of
using
> non-paged memory for the ramdisk driver. I think the reason it won’t
> allocate that much non-paged memory is because it is a limited resource.
> Instead use MmProbeAndLockPages() to keep your memory resident.
>
> Brian
>
> ----- Original Message -----
> From: “Andreas Roth”
> To: “NT Developers Interest List”
> Sent: Thursday, June 07, 2001 11:08 AM
> Subject: [ntdev] Allocate a large buffer for Virtual Disk
>
>
> > I’m using the Microsoft RAM Disk Driver for Windows 2000. In my system
are
> > 384MB RAM, but when i set the RAM Disk Size to 128MB the driver failed
to
> > allocate the memory. The driver uses ExAllocatePool(NonPagedPool,…). I
> > think the problem is the memory fragmentation (say me if i’m wrong). Any
> > suggestions ?
> >
> > A. Roth
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@sginet.com
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@arsoft-online.de
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@sginet.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

If you use non-paged pool, you MUST post the request for READ and WRITE to a
thread in the event that a page fault occurs while serving a page fault from
the memory manager.

Jamey

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Brian Palmer
Sent: Thursday, June 07, 2001 7:00 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Allocate a large buffer for Virtual Disk

I would suggest you allocate the memory from the paged pool
instead of using
non-paged memory for the ramdisk driver. I think the reason it won’t
allocate that much non-paged memory is because it is a limited resource.
Instead use MmProbeAndLockPages() to keep your memory resident.

Brian

----- Original Message -----
From: “Andreas Roth”
> To: “NT Developers Interest List”
> Sent: Thursday, June 07, 2001 11:08 AM
> Subject: [ntdev] Allocate a large buffer for Virtual Disk
>
>
> > I’m using the Microsoft RAM Disk Driver for Windows 2000. In my
> system are
> > 384MB RAM, but when i set the RAM Disk Size to 128MB the driver
> failed to
> > allocate the memory. The driver uses ExAllocatePool(NonPagedPool,…). I
> > think the problem is the memory fragmentation (say me if i’m wrong). Any
> > suggestions ?
> >
> > A. Roth
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@sginet.com
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

Jamey,

you are not quite right, if you lock the pages from the non-paged pool no
faults occur.

Max

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Jamey Kirby
Sent: Sunday, June 10, 2001 9:05 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Allocate a large buffer for Virtual Disk

If you use non-paged pool, you MUST post the request for READ and WRITE to a
thread in the event that a page fault occurs while serving a page fault from
the memory manager.

Jamey

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Brian Palmer
Sent: Thursday, June 07, 2001 7:00 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Allocate a large buffer for Virtual Disk

I would suggest you allocate the memory from the paged pool
instead of using
non-paged memory for the ramdisk driver. I think the reason it won’t
allocate that much non-paged memory is because it is a limited resource.
Instead use MmProbeAndLockPages() to keep your memory resident.

Brian

----- Original Message -----
From: “Andreas Roth”
> To: “NT Developers Interest List”
> Sent: Thursday, June 07, 2001 11:08 AM
> Subject: [ntdev] Allocate a large buffer for Virtual Disk
>
>
> > I’m using the Microsoft RAM Disk Driver for Windows 2000. In my
> system are
> > 384MB RAM, but when i set the RAM Disk Size to 128MB the driver
> failed to
> > allocate the memory. The driver uses ExAllocatePool(NonPagedPool,…). I
> > think the problem is the memory fragmentation (say me if i’m wrong). Any
> > suggestions ?
> >
> > A. Roth
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@sginet.com
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>


You are currently subscribed to ntdev as: xxxxx@acronis.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

If you are talking about *non*-paged pool, you are never going to get
faults. Ever. And I’m not sure you *can* lock non-paged pool.

Phil

-----Original Message-----
From: Max Lyadvinsky [mailto:xxxxx@acronis.com]
Sent: Sunday, June 10, 2001 11:01 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Allocate a large buffer for Virtual Disk

Jamey,

you are not quite right, if you lock the pages from the non-paged pool no
faults occur.

Max

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Jamey Kirby
Sent: Sunday, June 10, 2001 9:05 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Allocate a large buffer for Virtual Disk

If you use non-paged pool, you MUST post the request for READ and WRITE to a
thread in the event that a page fault occurs while serving a page fault from
the memory manager.

Jamey

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Brian Palmer
Sent: Thursday, June 07, 2001 7:00 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Allocate a large buffer for Virtual Disk

I would suggest you allocate the memory from the paged pool
instead of using
non-paged memory for the ramdisk driver. I think the reason it won’t
allocate that much non-paged memory is because it is a limited resource.
Instead use MmProbeAndLockPages() to keep your memory resident.

Brian

----- Original Message -----
From: “Andreas Roth”
> To: “NT Developers Interest List”
> Sent: Thursday, June 07, 2001 11:08 AM
> Subject: [ntdev] Allocate a large buffer for Virtual Disk
>
>
> > I’m using the Microsoft RAM Disk Driver for Windows 2000. In my
> system are
> > 384MB RAM, but when i set the RAM Disk Size to 128MB the driver
> failed to
> > allocate the memory. The driver uses ExAllocatePool(NonPagedPool,…). I
> > think the problem is the memory fragmentation (say me if i’m wrong). Any
> > suggestions ?
> >
> > A. Roth


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

sorry. I ment to say paged pool.

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Barila, Phil
Sent: Monday, June 11, 2001 8:25 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Allocate a large buffer for Virtual Disk

If you are talking about *non*-paged pool, you are never going to get
faults. Ever. And I’m not sure you *can* lock non-paged pool.

Phil

-----Original Message-----
From: Max Lyadvinsky [mailto:xxxxx@acronis.com]
Sent: Sunday, June 10, 2001 11:01 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Allocate a large buffer for Virtual Disk

Jamey,

you are not quite right, if you lock the pages from the non-paged pool no
faults occur.

Max

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Jamey Kirby
Sent: Sunday, June 10, 2001 9:05 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Allocate a large buffer for Virtual Disk

If you use non-paged pool, you MUST post the request for READ and
WRITE to a
thread in the event that a page fault occurs while serving a page
fault from
the memory manager.

Jamey

> -----Original Message-----
> From: xxxxx@lists.osr.com
> [mailto:xxxxx@lists.osr.com]On Behalf Of Brian Palmer
> Sent: Thursday, June 07, 2001 7:00 PM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Allocate a large buffer for Virtual Disk
>
>
> I would suggest you allocate the memory from the paged pool
> instead of using
> non-paged memory for the ramdisk driver. I think the reason it won’t
> allocate that much non-paged memory is because it is a limited resource.
> Instead use MmProbeAndLockPages() to keep your memory resident.
>
> Brian
>
> ----- Original Message -----
> From: “Andreas Roth”
> > To: “NT Developers Interest List”
> > Sent: Thursday, June 07, 2001 11:08 AM
> > Subject: [ntdev] Allocate a large buffer for Virtual Disk
> >
> >
> > > I’m using the Microsoft RAM Disk Driver for Windows 2000. In my
> > system are
> > > 384MB RAM, but when i set the RAM Disk Size to 128MB the driver
> > failed to
> > > allocate the memory. The driver uses
> ExAllocatePool(NonPagedPool,…). I
> > > think the problem is the memory fragmentation (say me if i’m
> wrong). Any
> > > suggestions ?
> > >
> > > A. Roth
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

If you are just doing this for one system, and not making a product,
on NT 4 you can get away with setting MAXMEM=64MB on the startup
line, then have a modified RamDisk driver use the Virtual addresses
from 84000000-8fffffff (if you had 512MB). The HAL maps in
the first 512MB of physical address space using 4MB pages, regardless
of whether there is actually physical memory behind it.

I’ve never tried this on Win2K.

In a similar vein, I believe that drivers loaded at boot time get VA’s from
this same space. On of the things on my list is to see if I can get a 384
MB chunk of memory in a driver loaded at boot time by leveraging this
boot time behavior.

Yet another technique is to only access the memory from a thread you’ve created,
where that thread is in a process that has mapped a large amount of physical
address space (again above MAXMEM) into UVA space. Its feasible to
to address 2GB this way.

-DH
----- Original Message -----
From: “Brian Palmer”
To: “NT Developers Interest List”
Sent: Thursday, June 07, 2001 10:00 PM
Subject: [ntdev] Re: Allocate a large buffer for Virtual Disk

> I would suggest you allocate the memory from the paged pool instead of using
> non-paged memory for the ramdisk driver. I think the reason it won’t
> allocate that much non-paged memory is because it is a limited resource.
> Instead use MmProbeAndLockPages() to keep your memory resident.
>
> Brian
>
> ----- Original Message -----
> From: “Andreas Roth”
> To: “NT Developers Interest List”
> Sent: Thursday, June 07, 2001 11:08 AM
> Subject: [ntdev] Allocate a large buffer for Virtual Disk
>
>
> > I’m using the Microsoft RAM Disk Driver for Windows 2000. In my system are
> > 384MB RAM, but when i set the RAM Disk Size to 128MB the driver failed to
> > allocate the memory. The driver uses ExAllocatePool(NonPagedPool,…). I
> > think the problem is the memory fragmentation (say me if i’m wrong). Any
> > suggestions ?
> >
> > A. Roth
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@sginet.com
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@syssoftsol.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

> Yet another technique is to only access the memory from a thread

you’ve created,
where that thread is in a process that has mapped a large amount
of physical
address space (again above MAXMEM) into UVA space. Its feasible to
to address 2GB this way.

Yes. This works… Since the system process has no user space, you have
almost the entire 2 gig to work with. Create a system thread in the system
process. Create a section object, associate it with a file or the page file
and then map it.

This is, in essence, a memory mapped file in kernel mode.

Jamey

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Dave Harvey
Sent: Tuesday, June 12, 2001 7:01 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Allocate a large buffer for Virtual Disk

If you are just doing this for one system, and not making a product,
on NT 4 you can get away with setting MAXMEM=64MB on the startup
line, then have a modified RamDisk driver use the Virtual addresses
from 84000000-8fffffff (if you had 512MB). The HAL maps in
the first 512MB of physical address space using 4MB pages, regardless
of whether there is actually physical memory behind it.

I’ve never tried this on Win2K.

In a similar vein, I believe that drivers loaded at boot time get
VA’s from
this same space. On of the things on my list is to see if I can get a 384
MB chunk of memory in a driver loaded at boot time by leveraging this
boot time behavior.

Yet another technique is to only access the memory from a thread
you’ve created,
where that thread is in a process that has mapped a large amount
of physical
address space (again above MAXMEM) into UVA space. Its feasible to
to address 2GB this way.

-DH
----- Original Message -----
From: “Brian Palmer”
> To: “NT Developers Interest List”
> Sent: Thursday, June 07, 2001 10:00 PM
> Subject: [ntdev] Re: Allocate a large buffer for Virtual Disk
>
>
> > I would suggest you allocate the memory from the paged pool
> instead of using
> > non-paged memory for the ramdisk driver. I think the reason it won’t
> > allocate that much non-paged memory is because it is a limited resource.
> > Instead use MmProbeAndLockPages() to keep your memory resident.
> >
> > Brian
> >
> > ----- Original Message -----
> > From: “Andreas Roth”
> > To: “NT Developers Interest List”
> > Sent: Thursday, June 07, 2001 11:08 AM
> > Subject: [ntdev] Allocate a large buffer for Virtual Disk
> >
> >
> > > I’m using the Microsoft RAM Disk Driver for Windows 2000. In
> my system are
> > > 384MB RAM, but when i set the RAM Disk Size to 128MB the
> driver failed to
> > > allocate the memory. The driver uses
> ExAllocatePool(NonPagedPool,…). I
> > > think the problem is the memory fragmentation (say me if i’m
> wrong). Any
> > > suggestions ?
> > >
> > > A. Roth
> > >
> > >
> > > —
> > > You are currently subscribed to ntdev as: xxxxx@sginet.com
> > > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> > >
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@syssoftsol.com
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

----- Original Message -----
From: “Jamey Kirby”
To: “NT Developers Interest List”
Sent: Wednesday, June 13, 2001 11:39 AM
Subject: [ntdev] Re: Allocate a large buffer for Virtual Disk

> > Yet another technique is to only access the memory from a thread
> > you’ve created,
> > where that thread is in a process that has mapped a large amount
> > of physical
> > address space (again above MAXMEM) into UVA space. Its feasible to
> > to address 2GB this way.
>
> Yes. This works… Since the system process has no user space, you have
> almost the entire 2 gig to work with. Create a system thread in the system
> process. Create a section object, associate it with a file or the page file
> and then map it.
You can also set MAXMEM low, and map the memory into the system processes UVA
as if it were 2G of “device” memory. In this case, there can be no paging,
and you can access the memory from within a system thread (but not a DPC
or arbitrary thread) at any IRQL.

-DH

>
> This is, in essence, a memory mapped file in kernel mode.
>
> Jamey
>
> > -----Original Message-----
> > From: xxxxx@lists.osr.com
> > [mailto:xxxxx@lists.osr.com]On Behalf Of Dave Harvey
> > Sent: Tuesday, June 12, 2001 7:01 PM
> > To: NT Developers Interest List
> > Subject: [ntdev] Re: Allocate a large buffer for Virtual Disk
> >
> >
> > If you are just doing this for one system, and not making a product,
> > on NT 4 you can get away with setting MAXMEM=64MB on the startup
> > line, then have a modified RamDisk driver use the Virtual addresses
> > from 84000000-8fffffff (if you had 512MB). The HAL maps in
> > the first 512MB of physical address space using 4MB pages, regardless
> > of whether there is actually physical memory behind it.
> >
> > I’ve never tried this on Win2K.
> >
> > In a similar vein, I believe that drivers loaded at boot time get
> > VA’s from
> > this same space. On of the things on my list is to see if I can get a 384
> > MB chunk of memory in a driver loaded at boot time by leveraging this
> > boot time behavior.
> >
> > Yet another technique is to only access the memory from a thread
> > you’ve created,
> > where that thread is in a process that has mapped a large amount
> > of physical
> > address space (again above MAXMEM) into UVA space. Its feasible to
> > to address 2GB this way.
> >
> > -DH
> > ----- Original Message -----
> > From: “Brian Palmer”
> > To: “NT Developers Interest List”
> > Sent: Thursday, June 07, 2001 10:00 PM
> > Subject: [ntdev] Re: Allocate a large buffer for Virtual Disk
> >
> >
> > > I would suggest you allocate the memory from the paged pool
> > instead of using
> > > non-paged memory for the ramdisk driver. I think the reason it won’t
> > > allocate that much non-paged memory is because it is a limited resource.
> > > Instead use MmProbeAndLockPages() to keep your memory resident.
> > >
> > > Brian
> > >
> > > ----- Original Message -----
> > > From: “Andreas Roth”
> > > To: “NT Developers Interest List”
> > > Sent: Thursday, June 07, 2001 11:08 AM
> > > Subject: [ntdev] Allocate a large buffer for Virtual Disk
> > >
> > >
> > > > I’m using the Microsoft RAM Disk Driver for Windows 2000. In
> > my system are
> > > > 384MB RAM, but when i set the RAM Disk Size to 128MB the
> > driver failed to
> > > > allocate the memory. The driver uses
> > ExAllocatePool(NonPagedPool,…). I
> > > > think the problem is the memory fragmentation (say me if i’m
> > wrong). Any
> > > > suggestions ?
> > > >
> > > > A. Roth
> > > >
> > > >
> > > > —
> > > > You are currently subscribed to ntdev as: xxxxx@sginet.com
> > > > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> > > >
> > >
> > >
> > > —
> > > You are currently subscribed to ntdev as: xxxxx@syssoftsol.com
> > > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
> >
> > —
> > You are currently subscribed to ntdev as: xxxxx@storagecraft.com
> > To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
> >
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@syssoftsol.com
> To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com


You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com