Date: Mon, 11 Mar 2013 09:11:03 -0700 From: Freddie Cash <fjwcash@gmail.com> To: Mark Saad <nonesuch@longcount.org> Cc: FreeBSD-Stable ML <freebsd-stable@freebsd.org> Subject: Re: netisr issues Message-ID: <CAOjFWZ5EC8w6FsjgLPskSEzcw=O6WRSsQf5jbMGFs90P7qVkqA@mail.gmail.com> In-Reply-To: <CAMXt9NY6-jm-DEBk6WN5PXgAd4%2BBND4WVfqiSdtqoKzyYcRm3Q@mail.gmail.com> References: <CAMXt9NY6-jm-DEBk6WN5PXgAd4%2BBND4WVfqiSdtqoKzyYcRm3Q@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Works if you set them in /etc/sysctl.conf. Haven't looked into it, but I think there's something in the startup that sets them to 0 after the kernel is loaded, so the loader.conf settings are overwritten. On Mon, Mar 11, 2013 at 7:42 AM, Mark Saad <nonesuch@longcount.org> wrote: > All > I am looking for some guidance on how to turn netisr back on, on a > 9.1-RELEASE and 9.1-STABLE box. It looks it stopped working as it did in > prior versions of FreeBSD . > I tested this on 9.1-RELEASE and 9.1-STABLE #0 r247804 built last monday. > > My question is this. If I enable the direct option in boot/loader.conf via > this > > net.isr.direct="1" > net.isr.direct_force="1" > > I do not get any expected result. > > root@chambers:~ # sysctl net.isr.direct > net.isr.direct: 0 > root@chambers:~ # sysctl net.isr.direct_force > net.isr.direct_force: 0 > > root@chambers:~ # netstat -Q > Configuration: > Setting Current Limit > Thread count 1 1 > Default queue limit 256 10240 > Dispatch policy direct n/a > Threads bound to CPUs disabled n/a > > .... > > > Am I missing something ? > > > -- > mark saad | nonesuch@longcount.org > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" > -- Freddie Cash fjwcash@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOjFWZ5EC8w6FsjgLPskSEzcw=O6WRSsQf5jbMGFs90P7qVkqA>