FEATURE: Implement 'make config' in /usr/src
It will be nice to create nice menu that will allow user disable/enable modules to build kernel cd /usr/src make config ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
netisr ambigios policy
From sys/net/netisr.c
switch (netisr_dispatch_policy) {
case NETISR_DISPATCH_DEFERRED:
netisr_direct_force = 0;
netisr_direct = 0;
break;
case NETISR_DISPATCH_HYBRID:
netisr_direct_force = 0;
netisr_direct = 1;
break;
case NETISR_DISPATCH_DIRECT:
netisr_direct_force = 1;
netisr_direct = 1;
break;
that having direct_force = 0 and direct = 0 it is DISPATCH_DEFFERED
but doing:
# sysctl net.isr
net.isr.numthreads: 4
net.isr.maxprot: 16
net.isr.defaultqlimit: 256
net.isr.maxqlimit: 10240
net.isr.bindthreads: 0
net.isr.maxthreads: 4
net.isr.direct: 0
net.isr.direct_force: 0
net.isr.dispatch: direct
you can see that net.isr.dispatch is 'direct'
I expect 'deffered' as it declared here:
static const struct netisr_dispatch_table_entry netisr_dispatch_table[] = {
{ NETISR_DISPATCH_DEFAULT, default },
{ NETISR_DISPATCH_DEFERRED, deferred },
{ NETISR_DISPATCH_HYBRID, hybrid },
{ NETISR_DISPATCH_DIRECT, direct },
Is this a BUG?
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: netisr ambigios policy
Здравствуйте, Коньков.
Вы писали 14 января 2012 г., 15:31:04:
КЕ From sys/net/netisr.c
КЕ switch (netisr_dispatch_policy) {
КЕ case NETISR_DISPATCH_DEFERRED:
КЕ netisr_direct_force = 0;
КЕ netisr_direct = 0;
КЕ break;
КЕ case NETISR_DISPATCH_HYBRID:
КЕ netisr_direct_force = 0;
КЕ netisr_direct = 1;
КЕ break;
КЕ case NETISR_DISPATCH_DIRECT:
КЕ netisr_direct_force = 1;
КЕ netisr_direct = 1;
КЕ break;
КЕ that having direct_force = 0 and direct = 0 it is DISPATCH_DEFFERED
КЕ but doing:
КЕ # sysctl net.isr
КЕ net.isr.numthreads: 4
КЕ net.isr.maxprot: 16
КЕ net.isr.defaultqlimit: 256
КЕ net.isr.maxqlimit: 10240
КЕ net.isr.bindthreads: 0
КЕ net.isr.maxthreads: 4
КЕ net.isr.direct: 0
КЕ net.isr.direct_force: 0
КЕ net.isr.dispatch: direct
КЕ you can see that net.isr.dispatch is 'direct'
КЕ I expect 'deffered' as it declared here:
КЕ static const struct netisr_dispatch_table_entry netisr_dispatch_table[] = {
КЕ { NETISR_DISPATCH_DEFAULT, default },
КЕ { NETISR_DISPATCH_DEFERRED, deferred },
КЕ { NETISR_DISPATCH_HYBRID, hybrid },
КЕ { NETISR_DISPATCH_DIRECT, direct },
КЕ Is this a BUG?
setting this to
net.isr.direct=1
net.isr.direct_force=1
in /boot/loader.conf
has no effect
# sysctl net.isr
net.isr.numthreads: 4
net.isr.maxprot: 16
net.isr.defaultqlimit: 256
net.isr.maxqlimit: 10240
net.isr.bindthreads: 0
net.isr.maxthreads: 4
net.isr.direct: 0
net.isr.direct_force: 0
net.isr.dispatch: direct
It seems has been broken in r49
--
С уважением,
Коньков mailto:kes-...@yandex.ru
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
[RESOLVED]: upgrading to r230059 cause slow network throughput
Здравствуйте, Коньков.
Вы писали 13 января 2012 г., 21:32:14:
КЕ I have tryed as ULE as SCHED_4BSD, no changes
КЕ in both cases low throughput
КЕ CPUload
КЕ http://piccy.info/view3/2478224/e5d7f208538d05d813411c34eb493a8f/orig/
КЕ if load
КЕ http://piccy.info/view3/2478228/bf8dca5fad12c1436092f4d6aaf2356f/orig/
КЕ looking on graphs CPU load it seems strange distribution...
КЕ it seems almost not scheduling ng_queue and netisr
КЕ last pid: 54347; load averages: 0.30, 0.28, 0.22 up
0+06:24:06 21:25:11
КЕ 273 processes: 5 running, 237 sleeping, 31 waiting
КЕ CPU 0: 0.0% user, 0.0% nice, 3.1% system, 0.4% interrupt, 96.5% idle
КЕ CPU 1: 3.5% user, 0.0% nice, 1.2% system, 0.4% interrupt, 94.9% idle
КЕ CPU 2: 2.0% user, 0.0% nice, 1.6% system, 0.4% interrupt, 96.1% idle
КЕ CPU 3: 0.0% user, 0.0% nice, 0.8% system, 3.1% interrupt, 96.1% idle
КЕ Mem: 310M Active, 1080M Inact, 179M Wired, 112M Buf, 354M Free
КЕ Swap: 3926M Total, 3926M Free
КЕ PID USERNAME PRI NICE SIZERES STATE C TIME WCPU COMMAND
КЕ11 root 155 ki31 0K32K CPU33 359:26 94.38% idle{idle:
cpu3}
КЕ11 root 155 ki31 0K32K CPU00 356:33 92.77% idle{idle:
cpu0}
КЕ11 root 155 ki31 0K32K RUN 1 345:23 89.60% idle{idle:
cpu1}
КЕ11 root 155 ki31 0K32K CPU22 340:20 85.35% idle{idle:
cpu2}
КЕ 3312 root400 15468K 6488K select 2 15:00 4.25% snmpd
КЕ12 root -60- 0K 248K WAIT0 7:20 1.07% intr{swi4:
clock}
КЕ12 root -92- 0K 248K WAIT3 12:06 0.29%
intr{irq266: re0}
КЕ 0 root -920 0K 152K - 3 6:45 0.05%
kernel{dummynet}
КЕ13 root -92- 0K32K sleep 1 1:39 0.00%
ng_queue{ng_queue1}
КЕ13 root -92- 0K32K sleep 1 1:39 0.00%
ng_queue{ng_queue3}
КЕ13 root -92- 0K32K sleep 3 1:39 0.00%
ng_queue{ng_queue0}
КЕ13 root -92- 0K32K sleep 0 1:39 0.00%
ng_queue{ng_queue2}
КЕ 6880 root 80 9592K 1300K nanslp 1 0:46 0.00% monitord
КЕ 0 root -160 0K 152K sched 1 0:43 0.00%
kernel{swapper}
КЕ 95148 root160 9756K 1452K pause 1 0:37 0.00% netstat
КЕ12 root -72- 0K 248K WAIT3 0:34 0.00% intr{swi1:
netisr 3}
КЕ15 root -16- 0K 8K - 3 0:28 0.00% yarrow
КЕ 1070 root400 10524K 4224K select 1 0:21 0.00% zebra
КЕ 2020 root30 -10 50664K 22824K select 3 0:20 0.00% mpd5{mpd5}
КЕ 7611 firebird30 -10 106M 65780K usem2 0:14 0.00%
fb_smp_server{fb_smp_server}
КЕ 1766 root400 9680K 1480K select 2 0:11 0.00% syslogd
КЕ 1909 bind400 69244K 55360K uwait 1 0:06 0.00% named{named}
КЕ 1909 bind400 69244K 55360K uwait 1 0:06 0.00% named{named}
КЕ 1909 bind400 69244K 55360K uwait 1 0:06 0.00% named{named}
КЕ 1909 bind400 69244K 55360K uwait 3 0:06 0.00% named{named}
КЕ 8 root16- 0K 8K syncer 0 0:06 0.00% syncer
КЕ 1909 bind 40 69244K 55360K kqread 2 0:06 0.00% named{named}
КЕ in compare to FreeBSD-9,
КЕ 10-CURRENT has only one {swi1: netisr 3}
КЕ 9- has four process: {swi1: netisr 0} {swi1: netisr 1}
КЕ {swi1: netisr 2} {swi1: netisr 3}
КЕ last pid: 40679; load averages: 2.38, 2.39, 2.28 up
2+05:31:50 21:23:43
КЕ 294 processes: 7 running, 269 sleeping, 18 waiting
КЕ CPU 0: 1.2% user, 0.0% nice, 20.4% system, 23.9% interrupt, 54.5% idle
КЕ CPU 1: 1.2% user, 0.0% nice, 10.6% system, 29.8% interrupt, 58.4% idle
КЕ CPU 2: 0.4% user, 0.0% nice, 10.2% system, 26.7% interrupt, 62.7% idle
КЕ CPU 3: 1.2% user, 0.0% nice, 16.1% system, 22.4% interrupt, 60.4% idle
КЕ Mem: 750M Active, 2700M Inact, 307M Wired, 83M Cache, 112M Buf, 58M Free
КЕ Swap: 4096M Total, 49M Used, 4047M Free, 1% Inuse
КЕ PID USERNAME PRI NICE SIZERES STATE C TIME WCPU COMMAND
КЕ11 root 155 ki31 0K32K RUN 1 37.1H 59.23% {idle: cpu1}
КЕ11 root 155 ki31 0K32K RUN 3 37.3H 58.79% {idle: cpu3}
КЕ11 root 155 ki31 0K32K RUN 2 36.8H 57.62% {idle: cpu2}
КЕ11 root 155 ki31 0K32K CPU00 34.9H 51.46% {idle: cpu0}
КЕ12 root -72- 0K 160K CPU22 778:00 39.99% {swi1:
netisr 3}
КЕ12 root -72- 0K 160K CPU11 558:58 22.56% {swi1:
netisr 1}
КЕ12 root -92- 0K 160K WAIT0 424:04 16.60% {irq256:
re0}
КЕ12 root -72- 0K 160K WAIT3 204:04 14.36% {swi1:
netisr 0}
КЕ12 root -72- 0K 160K WAIT1 224:14 7.62% {swi1:
netisr 2}
КЕ13 root -16- 0K32K sleep 0 123:28 5.37% {ng_queue0}
КЕ 6907 root230 15392K 5348K select 2 123:59
upgrading to r230059 cause slow network throughput
I have tryed as ULE as SCHED_4BSD, no changes
in both cases low throughput
CPUload http://piccy.info/view3/2478224/e5d7f208538d05d813411c34eb493a8f/orig/
if load http://piccy.info/view3/2478228/bf8dca5fad12c1436092f4d6aaf2356f/orig/
looking on graphs CPU load it seems strange distribution...
it seems almost not scheduling ng_queue and netisr
last pid: 54347; load averages: 0.30, 0.28, 0.22
up 0+06:24:06 21:25:11
273 processes: 5 running, 237 sleeping, 31 waiting
CPU 0: 0.0% user, 0.0% nice, 3.1% system, 0.4% interrupt, 96.5% idle
CPU 1: 3.5% user, 0.0% nice, 1.2% system, 0.4% interrupt, 94.9% idle
CPU 2: 2.0% user, 0.0% nice, 1.6% system, 0.4% interrupt, 96.1% idle
CPU 3: 0.0% user, 0.0% nice, 0.8% system, 3.1% interrupt, 96.1% idle
Mem: 310M Active, 1080M Inact, 179M Wired, 112M Buf, 354M Free
Swap: 3926M Total, 3926M Free
PID USERNAME PRI NICE SIZERES STATE C TIME WCPU COMMAND
11 root 155 ki31 0K32K CPU33 359:26 94.38% idle{idle: cpu3}
11 root 155 ki31 0K32K CPU00 356:33 92.77% idle{idle: cpu0}
11 root 155 ki31 0K32K RUN 1 345:23 89.60% idle{idle: cpu1}
11 root 155 ki31 0K32K CPU22 340:20 85.35% idle{idle: cpu2}
3312 root400 15468K 6488K select 2 15:00 4.25% snmpd
12 root -60- 0K 248K WAIT0 7:20 1.07% intr{swi4:
clock}
12 root -92- 0K 248K WAIT3 12:06 0.29% intr{irq266:
re0}
0 root -920 0K 152K - 3 6:45 0.05% kernel{dummynet}
13 root -92- 0K32K sleep 1 1:39 0.00%
ng_queue{ng_queue1}
13 root -92- 0K32K sleep 1 1:39 0.00%
ng_queue{ng_queue3}
13 root -92- 0K32K sleep 3 1:39 0.00%
ng_queue{ng_queue0}
13 root -92- 0K32K sleep 0 1:39 0.00%
ng_queue{ng_queue2}
6880 root 80 9592K 1300K nanslp 1 0:46 0.00% monitord
0 root -160 0K 152K sched 1 0:43 0.00% kernel{swapper}
95148 root160 9756K 1452K pause 1 0:37 0.00% netstat
12 root -72- 0K 248K WAIT3 0:34 0.00% intr{swi1:
netisr 3}
15 root -16- 0K 8K - 3 0:28 0.00% yarrow
1070 root400 10524K 4224K select 1 0:21 0.00% zebra
2020 root30 -10 50664K 22824K select 3 0:20 0.00% mpd5{mpd5}
7611 firebird30 -10 106M 65780K usem2 0:14 0.00%
fb_smp_server{fb_smp_server}
1766 root400 9680K 1480K select 2 0:11 0.00% syslogd
1909 bind400 69244K 55360K uwait 1 0:06 0.00% named{named}
1909 bind400 69244K 55360K uwait 1 0:06 0.00% named{named}
1909 bind400 69244K 55360K uwait 1 0:06 0.00% named{named}
1909 bind400 69244K 55360K uwait 3 0:06 0.00% named{named}
8 root16- 0K 8K syncer 0 0:06 0.00% syncer
1909 bind 40 69244K 55360K kqread 2 0:06 0.00% named{named}
in compare to FreeBSD-9,
10-CURRENT has only one {swi1: netisr 3}
9- has four process: {swi1: netisr 0} {swi1: netisr 1} {swi1: netisr 2}
{swi1: netisr 3}
last pid: 40679; load averages: 2.38, 2.39, 2.28 up
2+05:31:50 21:23:43
294 processes: 7 running, 269 sleeping, 18 waiting
CPU 0: 1.2% user, 0.0% nice, 20.4% system, 23.9% interrupt, 54.5% idle
CPU 1: 1.2% user, 0.0% nice, 10.6% system, 29.8% interrupt, 58.4% idle
CPU 2: 0.4% user, 0.0% nice, 10.2% system, 26.7% interrupt, 62.7% idle
CPU 3: 1.2% user, 0.0% nice, 16.1% system, 22.4% interrupt, 60.4% idle
Mem: 750M Active, 2700M Inact, 307M Wired, 83M Cache, 112M Buf, 58M Free
Swap: 4096M Total, 49M Used, 4047M Free, 1% Inuse
PID USERNAME PRI NICE SIZERES STATE C TIME WCPU COMMAND
11 root 155 ki31 0K32K RUN 1 37.1H 59.23% {idle: cpu1}
11 root 155 ki31 0K32K RUN 3 37.3H 58.79% {idle: cpu3}
11 root 155 ki31 0K32K RUN 2 36.8H 57.62% {idle: cpu2}
11 root 155 ki31 0K32K CPU00 34.9H 51.46% {idle: cpu0}
12 root -72- 0K 160K CPU22 778:00 39.99% {swi1: netisr 3}
12 root -72- 0K 160K CPU11 558:58 22.56% {swi1: netisr 1}
12 root -92- 0K 160K WAIT0 424:04 16.60% {irq256: re0}
12 root -72- 0K 160K WAIT3 204:04 14.36% {swi1: netisr 0}
12 root -72- 0K 160K WAIT1 224:14 7.62% {swi1: netisr 2}
13 root -16- 0K32K sleep 0 123:28 5.37% {ng_queue0}
6907 root230 15392K 5348K select 2 123:59 5.22% snmpd
13 root -16- 0K32K sleep 0 123:32 5.18% {ng_queue3}
13 root -16- 0K32K sleep 0 123:20 5.08% {ng_queue1}
13 root -16- 0K32K sleep 0 123:20 5.03% {ng_queue2}
3605
Re[2]: 9.0-RC1 panic in tcp_input: negative winow.
Здравствуйте, John.
Вы писали 20 декабря 2011 г., 16:52:44:
JB On Saturday, December 17, 2011 6:21:27 pm Pawel Jakub Dawidek wrote:
On Mon, Dec 12, 2011 at 11:00:23AM -0500, John Baldwin wrote:
An update. I've sent Pawel a testing patch to see if my hypothesis is
correct
(www.freebsd.org/~jhb/patches/tcp_negwin_test.patch). If it is then I
intend
to commit www.freebsd.org/~jhb/patches/tcp_negwin2.patch as the fix.
Unfortunately it paniced today. Take a look at:
http://people.freebsd.org/~pjd/misc/tcp_panic.jpg
JB Ok, the one use case I was worried about is happening regularly before your
JB panic, so that is good. Can you use gdb to figure out which call to
JB tcp_output() is actually panic'ing? I wonder if it is this case:
JB /*
JB * Return any desired output.
JB */
JB if (needoutput || (tp-t_flags TF_ACKNOW)) {
JB (void) tcp_output(tp);
JB /* XXX: Debug */
JB KASSERT(SEQ_GEQ(tp-rcv_adv, tp-rcv_nxt),
JB (tcp_input: negative window after ACK));
JB And if 'needoutput' is true, but TF_ACKNOW is not set, and tcp_output()
decides
JB to not do anything. I've updated tcp_negwin_test.patch to not panic if
that call
JB to tcp_output() doesn't actually send a packet. Please re-test.
# uname -a
FreeBSD meta-up 9.0-PRERELEASE FreeBSD 9.0-PRERELEASE #4: Sat Dec 24 13:59:20
EET 2011 @:/usr/obj/usr/src/sys/KES_KERN_v10 i386
rebooting once per day. Now I compile kernel with debug options.
Can you advice me which and where I find debug info when it will
reboting next time? so I can help to debug problem
--
С уважением,
Коньков mailto:kes-...@yandex.ru
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re[2]: Failure upgrading from 8-stable to current (9.0-Beta2)
Hi, Garrett.
No, that patch did not work.
because
+ tzsetup $${optC} -r; \
run current installed tzsetup which use libdialog.so
you must use just compiled one
/usr/obj/usr/src/usr.sbin/tzsetup/tzsetup
PS. I have 9-0Current 201101 upgrading to 9-0Beta2 20110925
I even try by hand setup ENV and manually run tzsetup from console
and got 'Undefined symbol _nc_wacs'
If I run '/usr/obj/usr/src/usr.sbin/tzsetup/tzsetup' from console it
works fine, so when I change Makefile as I noted below it works for me.
Вы писали 27 сентября 2011 г., 6:00:46:
GC 2011/9/26 Коньков Евгений kes-...@yandex.ru:
Hi
For me patch do not working
because tzsetup uses old tzsetup
I use this:
--- share/zoneinfo/Makefile (revision 224989)
+++ share/zoneinfo/Makefile (working copy)
@@ -72,7 +72,8 @@
optC=-C ${DESTDIR}; \
fi; \
echo Updating /etc/localtime; \
- tzsetup $${optC} -r; \
+ /usr/obj/usr/src/usr.sbin/tzsetup/tzsetup
$${optC} -r; \
fi; \
else \
echo Run tzsetup(8) manually to update /etc/localtime.; \
or run before world install
/usr/obj/usr/src/usr.sbin/tzsetup/tzsetup
I think it will be enough
GC Or the patch attached to
GC http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/160596 -- still open
GC after 3 weeks...
GC Thanks,
GC -Garrett
--
С уважением,
Коньков mailto:kes-...@yandex.ru
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Failure upgrading from 8-stable to current (9.0-Beta2)
Hi
For me patch do not working
because tzsetup uses old tzsetup
I use this:
--- share/zoneinfo/Makefile (revision 224989)
+++ share/zoneinfo/Makefile (working copy)
@@ -72,7 +72,8 @@
optC=-C ${DESTDIR}; \
fi; \
echo Updating /etc/localtime; \
- tzsetup $${optC} -r; \
+ /usr/obj/usr/src/usr.sbin/tzsetup/tzsetup
$${optC} -r; \
fi; \
else \
echo Run tzsetup(8) manually to update /etc/localtime.; \
or run before world install
/usr/obj/usr/src/usr.sbin/tzsetup/tzsetup
I think it will be enough
--
С уважением,
Коньков mailto:kes-...@yandex.ru
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
