On Fri, 13 Jul 2001, Martin Karsten wrote:
> 384/494/2048 mbuf clusters in use (current/peak/max)
>
> IMO the problem must have been introduced due to a change between versions
> 3.4 and 4.x. I'm not experienced with driver programming, the only obvious
> difference (at least with respect to the
Thanks for this hint, but it doesn't seem to help. Here's the output of
netstat -m after a test with packet losses:
386/608/8192 mbufs in use (current/peak/max):
385 mbufs allocated to data
1 mbufs allocated to packet headers
384/494/2048 mbuf clusters in use (current/peak/max)
11
Hello,
FWIW, I've recently built a test bench where I used P-III-450 PCs
running 4-port dc(4) NIC (DLINK DFE-570-TX).
The tests I've done have shown it's posible with the 4.2-R stock sources
(and a tailored kernel) to send AND simultaneously send more than 20k
packets/sec with a Packet Loss Rate
On Wed, 11 Jul 2001, Martin Karsten wrote:
> Greetings,
>
> I have observed the following behaviour on FreeBSD 4.x platforms (4.0 till
> 4.3 seem to be affected).
>
> When receiving a sufficiently fast stream of UDP packets (the borderline
> seems to be around 3,500 packets/sec for e.g. the 'xl'
Greetings,
I have observed the following behaviour on FreeBSD 4.x platforms (4.0 till
4.3 seem to be affected).
When receiving a sufficiently fast stream of UDP packets (the borderline
seems to be around 3,500 packets/sec for e.g. the 'xl' driver on a 450MHz
Pentium), an application on the recei
