| 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: Fri, 26 Jun 2009 16:04:04 +0200 From: Gallus <gall.cwpl@...il.com> To: linux-kernel@...r.kernel.org Subject: Kernel hard_start_xmit performance vs SOCK_RAW performance Hi, what path would you choose to rapidly generate packets: 1. Develop kernel space module and user space client tool. The tool would call the module through ioctl() passing the packet contents. The module would then construct sbk buffer and call hard_start_xmit. 2. Develop only user space client tool The tool would just sent packets through raw sockets. I'm wondering if amount of system calls in (1) solution will not be a problem? Which path is generally better? -- Regards, Gallus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists