netisr issues

[Mark Saad]

On Mon, Mar 11, 2013 at 12:11 PM, Freddie Cash <fjwcash at gmail.com> wrote:
> 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 at 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 at chambers:~ # sysctl net.isr.direct
>> net.isr.direct: 0
>> root at chambers:~ # sysctl net.isr.direct_force
>> net.isr.direct_force: 0
>>
>> root at 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 at longcount.org
>> _______________________________________________
>> freebsd-stable at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"
>
>
>
>
> --
> Freddie Cash
> fjwcash at gmail.com

Freddie
  When I tried to set them in /etc/sysctl.conf , sysctl stated they
were read-only .

[root at mkr2 /etc]# sysctl -w net.isr.direct=1
sysctl: oid 'net.isr.direct' is read only


[root at mkr2 /etc]# sysctl -w net.isr.direct_force=1
sysctl: oid 'net.isr.direct_force' is read only

--
mark saad | nonesuch at longcount.org