> On Dec 1, 2014, at 8:28 AM, Hans Petter Selasky <h...@selasky.org> wrote: > >> On 12/01/14 16:56, Alfred Perlstein wrote: >> >> >>>> On Dec 1, 2014, at 7:49 AM, Hans Petter Selasky <h...@selasky.org> wrote: >>>> >>>>> On 12/01/14 16:45, Alfred Perlstein wrote: >>>>> >>>>> Hi, >>>>> >>>>> It is quite early, actually: >>>>> >>>>> SYSINIT(sysctl, SI_SUB_KMEM, SI_ORDER_FIRST, sysctl_register_all, 0); >>>>> >>>>> In some parts of the machine independent, MI, code you neee to keep the >>>>> TUNABLE_FETCH'es, because its run before SI_SUB_KMEM ! >>>> >>>> Then it will not work unless I move the global n_queues sysctl creation >>>> into the driver's mod load function. >>>> >>>> Is that ok? >>> >>> Are you asking me? >> >> In soviet russia no one is ever sure whom to ask for permission to proceed. >> >> (Also you have significant commits to the driver so it makes sense. ) > > Ok, > > You need to check "sys/sys/kernel.h" for the full init order and figure out > where exactly your driver code is running and make sure that is running after > the SYSCTL/TUNABLE gets init.
Yes that is why it is being done by hand in the probe routine. I think proper thing might be a way to sort out how to get tunables to run at a driver load event? Is that possible? > > --HPS > > _______________________________________________ svn-src-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/svn-src-all To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"
