| implementation.ms (18568) | implementation.ms (18684) |
|---|---|
| 1.\" 2.\" ---------------------------------------------------------------------------- 3.\" "THE BEER-WARE LICENSE" (Revision 42): 4.\" <phk@login.dknet.dk> wrote this file. As long as you retain this notice you 5.\" can do whatever you want with this stuff. If we meet some day, and you think 6.\" this stuff is worth it, you can buy me a beer in return. Poul-Henning Kamp 7.\" ---------------------------------------------------------------------------- 8.\" | 1.\" 2.\" ---------------------------------------------------------------------------- 3.\" "THE BEER-WARE LICENSE" (Revision 42): 4.\" <phk@login.dknet.dk> wrote this file. As long as you retain this notice you 5.\" can do whatever you want with this stuff. If we meet some day, and you think 6.\" this stuff is worth it, you can buy me a beer in return. Poul-Henning Kamp 7.\" ---------------------------------------------------------------------------- 8.\" |
| 9.\" $Id: implementation.ms,v 1.1 1996/04/13 08:30:13 phk Exp $ | 9.\" $Id: implementation.ms,v 1.2 1996/09/29 18:36:11 phk Exp $ |
| 10.\" 11.ds RH Implementation 12.NH 13Implementation 14.PP 15A new malloc(3) implementation was written to meet the goals, 16and to the extent possible to address the shortcomings listed previously. 17.PP --- 96 unchanged lines hidden (view full) --- 114Instead they are ordered according to the address of the pages. 115Interestingly enough, in practice this comes out to almost the same 116thing performance wise. 117.PP 118It's not that surprising after all, it's the difference between 119following the crowd or actively directing where it can go, in both 120ways you can end up in the middle of it all. 121.PP | 10.\" 11.ds RH Implementation 12.NH 13Implementation 14.PP 15A new malloc(3) implementation was written to meet the goals, 16and to the extent possible to address the shortcomings listed previously. 17.PP --- 96 unchanged lines hidden (view full) --- 114Instead they are ordered according to the address of the pages. 115Interestingly enough, in practice this comes out to almost the same 116thing performance wise. 117.PP 118It's not that surprising after all, it's the difference between 119following the crowd or actively directing where it can go, in both 120ways you can end up in the middle of it all. 121.PP |
| 122The sideffect of this compromise is that it also uses less storage, | 122The side effect of this compromise is that it also uses less storage, |
| 123and the list never has to be reordered, all the ordering happens when 124pages are added or deleted. 125.PP 126It is an interesting twist to the implementation that the 127.B 128struct pginfo 129.R 130Is allocated with malloc. --- 92 unchanged lines hidden --- | 123and the list never has to be reordered, all the ordering happens when 124pages are added or deleted. 125.PP 126It is an interesting twist to the implementation that the 127.B 128struct pginfo 129.R 130Is allocated with malloc. --- 92 unchanged lines hidden --- |