Title: | DIGITAL UNIX (FORMERLY KNOWN AS DEC OSF/1) |
Notice: | Welcome to the Digital UNIX Conference |
Moderator: | SMURF::DENHAM |
Created: | Thu Mar 16 1995 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 10068 |
Total number of notes: | 35879 |
Hi, I have a customer with a selfwritten application (of course very complex) and he has the problem, that after a while the system can't get any mbufs at all. A simple ping just says "no buffer space available". He is using Digital UNIX V4.0B. My question is: What can I do or how can I write an application to eat all mbufs ? Is it just doing socket sends for a while without receiving anything ? regards Detlef. +-----------------------------------+----------------------------------+ | Detlef Schmier @RTO | Digital Equipment GmbH | | SBU, OEM/GY | Freischuetzstrasse 91 | | Field Application Engineer | D-81927 Muenchen | | Pub.Tel. +49-(0)89-9591 2752 | DTN 865-2752 | | Mobile +49-(0)171-3357582 | | | Fax # +49-(0)89-9591 1278 | DTN 865-1278 | +-----------------------------------+----------------------------------+ | eMail : [email protected] [email protected] | | URL : http://www.digital.de/infocenter/toem-gy/detlef.html | +----------------------------------------------------------------------+ [Posted by WWW Notes gateway]
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
9906.1 | easy to eat mbufs | SMURF::DUSTIN | Wed May 21 1997 14:36 | 12 | |
Yes, doing sends without doing recvs will cause the data to sit in the kernel socket buffers (default 32Kbytes). Since each user process can open 4096 fds, you could keep doing socket calls and sending 32K of data, but never do the recv, that would likely consume most of the memory on the system. That socket buffer space data is held in mbufs. You should see it all sitting there if you do "netstat -an" and look at the send queues. John |