lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 15 Jan 2008 08:47:07 -0600 From: "Chris Friesen" <cfriesen@...tel.com> To: Jarek Poplawski <jarkao2@...il.com> CC: David Miller <davem@...emloft.net>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: questions on NAPI processing latency and dropped network packets Jarek Poplawski wrote: > IMHO, checking this with a current stable, which probably you are going > to do some day, anyway, should be 100% acceptable: giving some input to > netdev, while still working for yourself. While I would love to do this, it's not that simple. 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. The blade in question uses CKRM which doesn't exist for newer kernels so the problem may simply be hidden by scheduling differences. 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). Basically, the number of changes required for our environment makes it difficult to just boot up the latest kernel. Chris -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists