On Mon, 18 Dec 2000, David S. Miller wrote:
> Date: Mon, 18 Dec 2000 13:54:56 -0500 (EST)
> From: "Richard B. Johnson" <root@chaos.analogic.com>
>
> 6/ Deallocates all the buffers by running down the linked-list.
>
> ...
>
> If the program deallocates all the buffers, as in (6) above, it will
> take even up to 1 whole minute!! At this time, there is an enormous
> amount of swap-file activity going on.
>
> How exactly are these buffers allocated/deallocated? Are you
> absolutely certain that the deallocation process does not make loads
> from or stores into the buffers as a free(3) implementation would?
>
> That would cause the pages to be sucked back from swap space.
>
Well I just use free(), nothing more, nothing special, just like
a typical data-base program. Free should just set a new break
address after the reclaimed data falls below some watermarks it
has established. Both malloc() and free(), use already allocated
data-space for their work-space (last time I looked at library code).
Cheers,
Dick Johnson
Penguin : Linux version 2.4.0 on an i686 machine (799.54 BogoMips).
"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 23 2000 - 21:00:22 EST