Date: Mon, 15 Oct 2001 09:13:37 -0700 (PDT) From: Matt Dillon <dillon@earth.backplane.com> To: mark tinguely <tinguely@web.cs.ndsu.nodak.edu> Cc: tmoestl@gmx.net, freebsd-hackers@FreeBSD.ORG, Patrick.Cipiere@udcast.com, tinguely@web.cs.ndsu.nodak.edu Subject: Re: contigfree, free what? Message-ID: <200110151613.f9FGDb854996@earth.backplane.com> References: <200110151610.f9FGAg433017@web.cs.ndsu.nodak.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
:
:I have a potentially silly question about contigmalloc1(), if the very
:unlikely occurance that the kernel VM space ran out, (the vm_map_findspace()
:failed) wouldn't we want to return the chunk of contiguous physical space
:back on the free queue before we return an allocation failure?
:
:--mark tinguely.
Ah, you came across that XXX comment? You are absolutely right. The
original implementor rushed writing the routine and didn't finish it.
contigmalloc() is only supposed to be used in the early life of the
system when its loading device drivers that need contiguous space,
so the case is not supposed to come up. Of course, that means that it
does come up from time to time :-(.
If you want to have a go at fixing it I will be happy to review.
-Matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200110151613.f9FGDb854996>