Date: Mon, 06 Sep 2010 00:49:35 -0500 From: Alan Cox <alan.l.cox@gmail.com> To: mdf@FreeBSD.org Cc: freebsd-hackers@freebsd.org, Nathan Whitehorn <nwhitehorn@freebsd.org> Subject: Re: UMA allocations from a specific physical range Message-ID: <4C8480EF.7050700@gmail.com> In-Reply-To: <AANLkTikrHr4y1qQhBEfAAaKB%2BxEwnm6ut1tDGTdMHovi@mail.gmail.com> References: <4C844609.9050505@freebsd.org> <AANLkTik59AOwPNgxXfjZnp74NGXvEsUFSN41RPk0WFF9@mail.gmail.com> <4C846DD2.4000507@freebsd.org> <AANLkTikrHr4y1qQhBEfAAaKB%2BxEwnm6ut1tDGTdMHovi@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
mdf@FreeBSD.org wrote: [snip] > IIRC the memory from vm_phys_alloc_contig() can be released like any > other page; the interface should just be fetching a specific page. > How far off is the page wire count? I'm assuming it's hitting the > assert that it's > 1? > > I think vm_page_free() is the right interface to free the page again, > so the wire count being off presumably means someone else wired it on > you; do you know what code did it? If no one else has a reference to > the page anymore then setting the wire count to 1, while a hack, > should be safe. > > Yes, vm_page_free() can be used to free a single page that was returned by vm_phys_alloc_contig(). Alan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C8480EF.7050700>