From: David Laight <David.Laight@ACULAB.COM>
To: netdev <netdev@vger.kernel.org>
Cc: "David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
'Eric Dumazet' <edumazet@google.com>
Subject: High packet rate udp receive
Date: Mon, 9 May 2022 16:55:13 +0000 [thread overview]
Message-ID: <06dc7df0afd344fc9aa656896e761d37@AcuMS.aculab.com> (raw)
I'm testing some high channel count RTP (UDP audio).
When I get much over 250000 receive packets/second the
network receive softint processing seems to overload
one cpu and then packets are silently discarded somewhere.
I (probably) can see all the packets in /sys/class/net/em2/statistics/rx_packets
but the counts from 'netstat -s' are a lot lower.
The packets are destined for a lot of UDP sockets - each gets 50/sec.
These can't be 'connected' because the source address is allowed to change.
For testing the source IP is pretty fixed.
But I've not tried to look for the actual bottleneck.
Are we stuck with one cpu doing all the ethernet, IP and UDP
receive processing?
(and the end of transmit reaping).
Or is there a way to get another cpu to do some of the work?
Since this is UDP things like gro can't help.
We do have to handle very large numbers of packets.
Would a multi-queue ethernet adapter help?
This system has a BCM5720 (tg3 driver) which I don't think is multi-Q.
OTOH I've also had issues with a similar packet rate on an intel
nic that would be multi-q because the interrupt mitigation logic
is completely broken for high packet rates.
Only increasing the ring size to 4096 stopped it dropping packets.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next reply other threads:[~2022-05-09 16:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 16:55 David Laight [this message]
2022-05-09 17:00 ` High packet rate udp receive Eric Dumazet
2022-05-09 17:09 ` Dave Taht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=06dc7df0afd344fc9aa656896e761d37@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.