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: Wed, 14 Oct 2009 22:34:17 +0200 From: Luca Deri <deri@...p.org> To: David Miller <davem@...emloft.net> Cc: bcook@...intsys.com, brad.doctor@...il.com, netdev@...r.kernel.org Subject: Re: PF_RING: Include in main line kernel? David so do you want me to start porting PF_RING facilities into PF_PACKET? As I have said I;m not against this: my goal is to include this work into the linux kernel, as it has been separate for too long. Luca On Oct 14, 2009, at 10:29 PM, David Miller wrote: > From: Luca Deri <deri@...p.org> > Date: Wed, 14 Oct 2009 22:26:25 +0200 > >> I agree that some PF_RING features could be merged into >> PF_PACKET. However PF_RING is not just about improving packet capture >> but it implements facilities that can be used by many monitoring >> applications including, packet balancing, reflection, layer-7 packet >> filtering, pf_ring socket clustering just to name a few. You can read >> about PF_RING feature into this tutorial: >> http://luca.ntop.org/IM2009_Tutorial.pdf > > I've already researched several times what PF_RING does and > is capable of doing, and my position still stands that none of > it can't be added to existing facilities. > > It's been an out of tree hack for years, and if it stays as > a seperate facility it's likely to stay that way. -- 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