Hi everyone,
I was wondering if there is a way to flush out pages in memory that
might not be required. I have a device driver that allocates 16 distict
buffers each 32K in size. This is done with a bus_dma call as they will
be accessed by a PCI device. The problem is that if I do a compile on
Sean McNeil wrote:
Hi everyone,
I was wondering if there is a way to flush out pages in memory that
might not be required. I have a device driver that allocates 16 distict
buffers each 32K in size. This is done with a bus_dma call as they will
be accessed by a PCI device. The problem is
Yes, thanks for the clarification. I still am inclined to believe,
though, that the disk driver is what is fragmenting the physical memory
with disk cacheing. It is only a theory, but it sounded plausible.
Thanks again,
Sean
On Tue, 2003-11-25 at 00:13, Maxime Henrion wrote:
Sean McNeil
Sean McNeil wrote:
Yes, thanks for the clarification. I still am inclined to believe,
though, that the disk driver is what is fragmenting the physical memory
with disk cacheing. It is only a theory, but it sounded plausible.
Maybe, but the root cause is not the disk caching. It may be that
Oh, I absolutely agree. I do not want any hacks. I was hoping that
there might be an existing mechanism that was in place that would allow
for the purging of unused physical pages by resource hogs.
I am reminded of an old OS I was fond of: AmigaOS. It had a real nice
feature where
On Tuesday 25 November 2003 18:43, Maxime Henrion wrote:
If I remember correctly, Alan Cox intended to write a binary buddy
allocator to handle the physical address space (or do coalescing another
way, I'm not sure...) so that this particular problem is solved.
Another way to solve it is the
Perfect!! This is exactly the thing I need. I will investigate. Memory
is an option, but this project is pretty much done. Knowing how to do
the bktr approach is something worth the excercise.
More RAM won't teach me anything new ;-)
Sean
On Tue, 2003-11-25 at 16:09, Daniel O'Connor wrote:
