| 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
| ||
|
Message-ID: <80769D7B14936844A23C0C43D9FBCF0F13E0F9F5@orsmsx501.amr.corp.intel.com> Date: Wed, 13 Aug 2008 15:06:35 -0700 From: "Duyck, Alexander H" <alexander.h.duyck@...el.com> To: "netdev@...r.kernel.org" <netdev@...r.kernel.org> CC: "davem@...emloft.net" <davem@...emloft.net>, "shemminger@...l.org" <shemminger@...l.org> Subject: Question on how to select specific tx queues for tx multiqueue in 2.6.27 Is there a way in 2.6.27 to specify queue that a specific traffic type goes to in user space? Using the multiqueue implementation in 2.6.26 it was possible to setup a multiqueue prio qdisc on the device and then target traffic to specific bands via tc which in turn would place the traffic on specific queues. Below are the two use cases that are currently failing. Case 1: Filter arp traffic to a specific queue based on the ethertype being ETH_P_ARP Current issue: all traffic is routed to queue 0 Case 2: Filter ip traffic to a specific queue based on source/destination port number or ip address. Current issue: traffic is routed to queue based on hash value determined by simple_tx_hash At this point it appears 2.6.27 broke something that used to work in 2.6.2[3456], what should we do at this point to get multiqueue tx back to having the same user space configuration that worked before? I would be glad to help provide more detail and/or testing of patches. Thanks, Alex -- 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