mbuf autotuning effect

[Adrian Chadd]

On 7 September 2013 12:21, hiren panchasara <hiren.panchasara at gmail.com>wrote:

>
> On Sep 6, 2013 8:26 PM, "Warner Losh" <imp at bsdimp.com> wrote:
> >
> >
> > On Sep 6, 2013, at 7:11 PM, Adrian Chadd wrote:
> >
> > > Yeah, why is VM_KMEM_SIZE only 12mbyte for MIPS? That's a little low
> for a
> > > platform that has a direct map that's slightly larger than 12mb :)
> > >
> > > Warner? Juli?
> >
> > All architectures have it at 12MB, except sparc64 where it is 16MB. This
> can be changed with the options VM_KMEM_SIZE=xxxxx in the config file.
>
> Right. Does that mean for any platform, if we do not have nmbclusters
> pre-set in kmeminit() than we will always have pretty low value of
> vm_kmem_size. And because of that, if maxmbufmem is not pre-set (via
> loader.conf) inside tunable_mbinit() , we will have very low value for
> maxmbufmem too.
>
> I hope (partially believe) that my understanding is not entirely correct.
> Because if its correct, we arw depending on loader.conf instead of actually
> auto tuning.
>
> Thanks,
> Hiren
>
>
.. so how's this work on i386? ARM?




-adrian