In message <[EMAIL PROTECTED]>, "Daniel C. Sobral" writes: >OTOH, the *only* way to get non-overcommit to FreeBSD is for someone who >*wants* that feature to sit down and code it. It won't happen otherwise. So, out of idle curiousity: If, somewhere down the road, I know the kernel well enough to attempt such a thing, what would the interest level be in merging such a feature? -s To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Re: [hackers] Re: Setting memory allocators for ... Peter Seebach
- Re: [hackers] Re: Setting memory allocators for ... Tony Finch
- Re: [hackers] Re: Setting memory allocators for ... Peter Seebach
- Re: [hackers] Re: Setting memory allocators for ... Lyndon Nerenberg
- Re: [hackers] Re: Setting memory allocators for ... Tony Finch
- Re: [hackers] Re: Setting memory allocators for ... Drew Eckhardt
- Re: [hackers] Re: Setting memory allocators for ... Tony Finch
- Re: [hackers] Re: Setting memory allocators for ... Maxime Henrion
- Re: [hackers] Re: Setting memory allocators for ... Tony Finch
- Re: Setting memory allocators for library functions. Daniel C. Sobral
- Re: Setting memory allocators for library functions. Peter Seebach
- Re: Setting memory allocators for library functi... Warner Losh
- Re: Setting memory allocators for library functi... Archie Cobbs
- Re: Setting memory allocators for library functi... Julian Elischer
- Re: Setting memory allocators for library functi... Peter Seebach
- Re: Setting memory allocators for library functi... Daniel C. Sobral
- Re: Setting memory allocators for library functi... Peter Seebach
- Re: Setting memory allocators for library functi... Peter Dufault
- Re: Setting memory allocators for library functi... Matt Dillon
- Re: Setting memory allocators for library functi... Daniel C. Sobral
- Re: Setting memory allocators for library functi... Matt Dillon