Subject: Re: mbuf socket options leak?
To: Robert Dobbs <banshee@gabriella.resort.com>
From: Jan-Hinrich Fessel <oskar@zappa.unna.Ping.DE>
List: current-users
Date: 01/12/1995 08:29:56
In message <199501120124.BAA00198@gabriella.resort.com>you write:
->Could someone else confirm the existance of a leak of socket option
->mbufs in netbsd -current kernel built 1/2/95

no, but on the last kernel before the eisa_machdep.h
(maybe this is simply plain 1.0)
zappa# netstat -m
98 mbufs in use:
        2 mbufs allocated to data
        1 mbufs allocated to packet headers
        69 mbufs allocated to protocol control blocks
        26 mbufs allocated to socket names and addresses
2/24 mapped pages in use
60 Kbytes allocated to network (26% in use)
0 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines
zappa# ping klecks
PING klecks.unna.ping.de (193.100.14.22): 56 data bytes
64 bytes from 193.100.14.22: icmp_seq=0 ttl=255 time=3.520 ms
64 bytes from 193.100.14.22: icmp_seq=1 ttl=255 time=2.107 ms
^C
--- klecks.unna.ping.de ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 2.107/2.813/3.520 ms
zappa# netstat -m
99 mbufs in use:
        2 mbufs allocated to data
        1 mbufs allocated to packet headers
        69 mbufs allocated to protocol control blocks
        26 mbufs allocated to socket names and addresses
        1 mbufs allocated to socket options
2/24 mapped pages in use
60 Kbytes allocated to network (27% in use)
0 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines
zappa# ping lilly
PING lilly.ping.de (193.100.14.2): 56 data bytes
ping: sendto: No route to host
ping: wrote lilly.ping.de 64 chars, ret=-1
ping: sendto: No route to host
ping: wrote lilly.ping.de 64 chars, ret=-1
^C
--- lilly.ping.de ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss
zappa# netstat -m
129 mbufs in use:
        23 mbufs allocated to data
        1 mbufs allocated to packet headers
        75 mbufs allocated to protocol control blocks
        28 mbufs allocated to socket names and addresses
        2 mbufs allocated to socket options
1/24 mapped pages in use
64 Kbytes allocated to network (28% in use)
0 requests for memory denied
0 requests for memory delayed
0 calls to protocol drain routines

This is during no connected SLIP/PPP session.
When SLIP/PPP is connected I get very often 
"no buffer space available" even though I have options GATEWAY
set.
This problem appears more often with PPP than with CSLIP.

When this occurs, there is no way to free up some mbufs
other than just dropping the connection.

Gruesse
       Oskar

 ==============================================================================
 					Tragbar ist, was nicht herunterfaellt.
						    oskar@zappa.unna.ping.de
 ==============================================================================