Re: questions on NAPI processing latency and dropped network packets
From: Chris Friesen
Date: Tue Jan 15 2008 - 12:15:16 EST
Radoslaw Szkodzinski (AstralStorm) wrote:
On Tue, 15 Jan 2008 08:47:07 -0600
"Chris Friesen" <cfriesen@xxxxxxxxxx> wrote:
Some of our hardware is not supported on mainline, so we need per-kernel
version patches to even bring up the blade. The blades netboot via a
jumbo-frame network, so kernel extensions are needed to handle setting
the MTU before mounting the rootfs.
Why? Can't you use a small initramfs to set it up?
Sure, if we changed our build system, engineered a suitable small
userspace, etc. At this point it's easier to maintain a small patch to
the kernel dhcp parsing code so that we can specify mtu.
The blade in question uses CKRM
which doesn't exist for newer kernels so the problem may simply be
hidden by scheduling differences.
Current spiritual successor is Ingo's realtime patchset I guess.
I think the group scheduling stuff for CFS is closer, but there are
design and API differences that would require us to rework our system.
The userspace application uses other
kernel features that are not in mainline (and likely some of them won't
ever be in mainline--I know because I've tried).
What would these be? Some proc or sysfs files that were removed or
renamed?
Maybe they can be worked around w/o changing the application at all, or
very minor changes.
No, more than proc/sysfs. Things like notification of process state
change (think like SIGCHLD but sent to arbitrary processes), additional
messaging protocol families, oom-killer protection, dirty page
monitoring, backwards compatibility for "dcbz" on the ppc970, nested
alternate signal stacks, and many others. Between our kernel vendor's
patches and our own, there are something like 600 patches applied to the
mainline kernel.
Also, be sure to check if there are pauses with other CPU hogs.
With the sctp hash patch applied we're now sitting with 45% cpu free on
one cpu, and about 25% free on the other, and we're still seeing
periodic bursts of rx fifo loss. It's wierd. Still trying to figure
out what's going on.
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/