Re: Maximum NIC interrupts
- From: Nash Nipples <trashy_bumper@xxxxxxxxx>
- Date: Wed, 26 Dec 2007 08:10:30 -0800 (PST)
Dear Jordi,
In theory, on a Gigabit link you get 1 000 000 000 bits * second.
By default you have the MTU set to 1500 bytes which makes ~12 000 bits.
1 000 000 000 / 12 000 = ~ 83 333 packets per second.
83 333 packets per second makes 0.083333 packets per microsecond.
1 / 0.08333 = 12.0 microseconds per packet. Thus one can interrupt CPU
at a rate of ~83 333 times per second. If you use lower packets sizes you
might get even more funny numbers.
8000 is a quiet low number. The driver was developed by guys
at Intel. I don't see a reason to worry.
By the way they have products with Interrupt Moderation.
http://www.intel.com/design/network/applnots/ap450.htm
The question is really amazing. Thanks, it have tickled me big time.
Sincerely,
Nash
----- Original Message ----
From: Jordi Espasa Clofent <jordi.espasa@xxxxxxxxxxx>
To: freebsd-net@xxxxxxxxxxx
Sent: Wednesday, December 26, 2007 12:12:55 PM
Subject: Re: Maximum NIC interrupts
OK, I'll try to explain in another way.
While I've done network performance test I've monitored the IRQ rate,
and, for example, it's a 7000/8000 interrupts per second in every NIC
(I
use 2 NICs in a bridge). The question is
¿how can I know if this irq rate is too high or not? ¿how can I know
if
I'm closer to device limits, or kernel limits?
I want to say that I'm don't know if 8000 irq per second means a high
IRQ use or a lower user.
I hope I've explained better at this time.
--
Thanks,
Jordi Espasa Clofent
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: Maximum NIC interrupts
- From: Jack Vogel
- Re: Maximum NIC interrupts
- Prev by Date: Re: Packet loss every 30.999 seconds
- Next by Date: Re: kern/119036: [netipsec] [patch] enc(4) and dummynet together produce kernel panics
- Previous by thread: Re: Maximum NIC interrupts
- Next by thread: Re: Maximum NIC interrupts
- Index(es):
Relevant Pages
- [PATCH 19-rc1] Fix typos in /Documentation : T
... If the request is not yet sent to userspace AND the signal is not ... +NAPI
works by shutting down event interrupts when there's work and ... The core layer invokes
devices to send packets in a round robin format. ... Correct a reference to free'ed memory
during controller ... (Linux-Kernel) - Re: Ethernet card receiving influenced by CPU speed?
... it usually shows up in nics and video cards. ... Frames are the "packets"
used to send ethernet signals/data on the ... (comp.os.linux.networking) - Re: Handling 100.000 packets/sec or more
... |goes as|high as 10 and the interface is losing packets ... the interface won't
send interrupts to ... (freebsd-net) - Re: Handling 100.000 packets/sec or more
... Adrian Penisoara writes: ... the interface won't send interrupts to ...
total number of mbufs available to the system. ... We got ingress filtering so the packets
go no further ... (freebsd-net) - Re: Polling tuning and performance
... I'm not exactly tied to polling. ... Never mind the fact that bgeand the underlying
hardware ... sucking in packets as fast as possible with minimal loss. ... Context
switches and interrupts are both shown. ... (freebsd-performance)