In nlc.lists.freebsd-current you wrote:
> If you looked at the "prgram" (term used loosely) it touches every bit of
> memory it allocates.
I seemed to have overlooked the bit where you wrote deadbeef. I took a
closer look.
What I think is happening is that as the blocks are allocated and then
tou
On 5 Feb 1999, John Saunders wrote:
> In nlc.lists.freebsd-current you wrote:
> > It succeeds as per allocating the memory until the swap is full. But, when
>
> Malloc's don't cause swap space allocation. Theoretically a process can
> malloc all of it's virtual address space so long as it doesn't
In nlc.lists.freebsd-current you wrote:
> It succeeds as per allocating the memory until the swap is full. But, when
Malloc's don't cause swap space allocation. Theoretically a process can
malloc all of it's virtual address space so long as it doesn't touch
the pages.
> it starts the reading/free
If I do a little
--- swap_pager.c.orig Thu Feb 4 23:30:43 1999
+++ swap_pager.cThu Feb 4 23:31:22 1999
@@ -203,8 +203,10 @@
swp_sizecheck()
{
if (vm_swap_size < nswap_lowat) {
+/*
if (swap_pager_full == 0)
printf("swap_pager: out of swap
