This is interesting, and demonstrates what I have been seeing, however OpenBSD obviously has other issues with it's mmap implementation entirely separate from this discussion.
The case we are discussing is only about the choice of search technique used during the allocation of the mmap region from available free space.. an area in which FreeBSD and NetBSD clearly lag behind OpenBSD. This would in no way effect the performance of using the region after it has been allocated. Seeya...Q On Thu, 2003-10-23 at 06:42, Andy wrote: > On Wed, Oct 22, 2003 at 04:50:58PM +0100, Bruce M Simpson wrote: > > On Wed, Oct 22, 2003 at 09:40:44AM -0500, Dan Nelson wrote: > > > > The actual commit quote reads: > > > > > > > > "use a red-black tree to find entries in the vm_map. augment the > > > > red-black tree to find free space between entries. speeds up memory > > > > allocation, etc..." > > > > > > > > I am wondering if there is a compelling reason why the technique used > > > > by OpenBSD could not be adapted to FreeBSD's VM system. > > > > > > Probably just a case of "too much to do and not enough people to do > > > it". FreeBSD already has sys/tree.h, which provides the red-black tree > > > macros. > > > > Now accepting patches! > > You might want to have a look at fefe's research > before you take the OpenBSD way. > > http://bulk.fefe.de/scalability/ > > aha > _______________________________________________ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "[EMAIL PROTECTED]" _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"