Re: heavy network load

I tested your patch (sched_ule.c.diff).
Then this network problem was solved!

Thank you.


patched & make kernel & rebooted & ping test:

katsuji_at_hexley% ping 192.168.0.6
PING 192.168.0.6 (192.168.0.6): 56 data bytes
64 bytes from 192.168.0.6: icmp_seq=0 ttl=64 time=0.457 ms
64 bytes from 192.168.0.6: icmp_seq=1 ttl=64 time=0.508 ms
64 bytes from 192.168.0.6: icmp_seq=2 ttl=64 time=0.700 ms
64 bytes from 192.168.0.6: icmp_seq=3 ttl=64 time=0.505 ms
64 bytes from 192.168.0.6: icmp_seq=4 ttl=64 time=0.616 ms
64 bytes from 192.168.0.6: icmp_seq=5 ttl=64 time=0.535 ms
64 bytes from 192.168.0.6: icmp_seq=6 ttl=64 time=0.630 ms
64 bytes from 192.168.0.6: icmp_seq=7 ttl=64 time=0.557 ms
64 bytes from 192.168.0.6: icmp_seq=8 ttl=64 time=0.549 ms
64 bytes from 192.168.0.6: icmp_seq=9 ttl=64 time=0.431 ms
^C
--- 192.168.0.6 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.431/0.549/0.700/0.078 ms


On 10/7/07, Christian S.J. Peron <csjp_at_freebsd.org> wrote:
> The original author of the scheduler has come up with this patch
> which should fix the issue. Please test the attached patch.
>
> On Sat, Oct 06, 2007 at 02:49:01PM +0900, Katsuji Ishikawa wrote:
> > Hi .
> > I use -CURRENT on Parallels Desktop(Mac OS X). It works very fine.
> > But today I csup'ed and installed these. After that, I encountered
> > network problem..
> >
> >
> > Details:
> >
> > Host: Parallels Desktop (Mac OS X) , 192.168.0.3
> > Guest: FreeBSD-CURRENT , 192.168.0.6
> >
> > before (Old current)
> > katsuji_at_hexley% ping 192.168.0.6
> > PING 192.168.0.6 (192.168.0.6): 56 data bytes
> > 64 bytes from 192.168.0.6: icmp_seq=0 ttl=64 time=0.462 ms
> > 64 bytes from 192.168.0.6: icmp_seq=1 ttl=64 time=0.623 ms
> > 64 bytes from 192.168.0.6: icmp_seq=2 ttl=64 time=0.497 ms
> > 64 bytes from 192.168.0.6: icmp_seq=3 ttl=64 time=0.571 ms
> > 64 bytes from 192.168.0.6: icmp_seq=4 ttl=64 time=0.610 ms
> > 64 bytes from 192.168.0.6: icmp_seq=5 ttl=64 time=0.510 ms
> > ^C
> > --- 192.168.0.6 ping statistics ---
> > 6 packets transmitted, 6 packets received, 0% packet loss
> > round-trip min/avg/max/stddev = 0.462/0.545/0.623/0.060 ms
> >
> >
> > after (csuped today, occured packet loss...)
> > katsuji_at_hexley% ping 192.168.0.6
> > PING 192.168.0.6 (192.168.0.6): 56 data bytes
> > 64 bytes from 192.168.0.6: icmp_seq=0 ttl=64 time=4397.146 ms
> > 64 bytes from 192.168.0.6: icmp_seq=1 ttl=64 time=3397.082 ms
> > 64 bytes from 192.168.0.6: icmp_seq=2 ttl=64 time=2397.021 ms
> > 64 bytes from 192.168.0.6: icmp_seq=3 ttl=64 time=1395.493 ms
> > 64 bytes from 192.168.0.6: icmp_seq=4 ttl=64 time=393.692 ms
> > ^C
> > --- 192.168.0.6 ping statistics ---
> > 11 packets transmitted, 5 packets received, 54% packet loss
> > round-trip min/avg/max/stddev = 393.692/2396.087/4397.146/1415.415 ms
> >
> >
> > kernel configuration:
> >
> > katsuji_at_seven% cat ULE3                         [/sys/i386/conf]
> > include         GENERIC
> > ident           ULE3
> >
> > nooptions       SCHED_4BSD
> > options         SCHED_ULE
> >
> >
> > Have you any good ideas?
> >
> > Regards,
> >
> > --
> > Katsuji ISHIKAWA <k.ishish_at_gmail.com>
> > _______________________________________________
> > freebsd-current_at_freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>
> --
> Christian S.J. Peron
> csjp_at_FreeBSD.ORG
> FreeBSD Committer
>
>


-- 
Katsuji ISHIKAWA <k.ishish_at_gmail.com>