vmem(9) with M_FIRSTFIT

[Navdeep Parhar]

I'm trying to use vmem with M_FIRSTFIT strategy but it causes an
assertion failure in vmem_xalloc.  The problem is that qc_import sets
M_BESTFIT in the flags passed to it before passing them on to
vmem_xalloc.  vmem_xalloc then complains because both FIRSTFIT and
BESTFIT are set.

Does anyone know why qc_import insists on M_BESTFIT?  Is it safe to
change it as shown here?

if ((flags & VMEM_FITMASK) == 0)
	flags |= M_BESTFIT;

Regards,
Navdeep


(kgdb) p panicstr
$4 = 0xffffffff814ed960 "Assertion strat == M_BESTFIT || strat ==
M_FIRSTFIT failed at /usr/src/sys/kern/subr_vmem.c:1113"
(kgdb) bt
...
#10 0xffffffff808e2a38 in kassert_panic (fmt=<value optimized out>) at
/usr/src/sys/kern/kern_shutdown.c:644
#11 0xffffffff80931ac4 in vmem_xalloc (vm=0xfffff800cc1dd000,
size0=<value optimized out>, align=0, phase=0,
    nocross=0, minaddr=0, maxaddr=<value optimized out>, flags=<value
optimized out>, addrp=0x12)
    at /usr/src/sys/kern/subr_vmem.c:1113
#12 0xffffffff80933bcc in qc_import (arg=0xfffff800cc1dd488,
store=0xfffff800475a6418, cnt=125,
    flags=<value optimized out>) at /usr/src/sys/kern/subr_vmem.c:507
#13 0xffffffff80b5ee00 in uma_zalloc_arg (zone=0xfffff8001345d480,
udata=0x0, flags=4097)
    at /usr/src/sys/vm/uma_core.c:2535
#14 0xffffffff809319e9 in vmem_alloc (vm=0xfffff800cc1dd000, size=<value
optimized out>, flags=4097,
    addrp=0xfffffe0238422868) at uma.h:336
#15 0xffffffff809a955c in do_setopt_tx_throttle (so=0xfffff80047b95000,
sopt=<value optimized out>)
    at /usr/src/sys/net/flow_throttle.c:379
...