sys/netinet/in_pcbgroup.c

65  * hardware work distribution strategies such as RSS.  In this construction,
72  * example, Toeplitz, specified by RSS, introduced a significant overhead if
76  * non-RSS interfaces.
83  * model, such as RSS or similar approaches taken in embedded network boards.
90  * When RSS is used, certain connection group parameters, such as the number
91  * of groups, are provided by the RSS implementation, found in in_rss.c.
119  * Hook netisr thread reconfiguration events, and propagate those to RSS so
149 #ifdef RSS
151 	 * If we're using RSS, then RSS determines the number of connection
152 	 * groups to use: one connection group per RSS bucket.  If for some
153 	 * reason RSS isn't able to provide a number of buckets, disable
164 	 * do dynamic rebalancing a la RSS, we'll need similar logic here.
182 		 * Initialise notional affinity of the pcbgroup -- for RSS,
184 		 * the non-RSS case, just round robin for the time being.
187 		 * both pcbgroup and RSS layers -- does that mean that we
188 		 * should migrate it all from RSS to here, and just leave RSS
191 #ifdef RSS
225  * index.  Where RSS is supported, try to align bucket selection with RSS CPU
232 #ifdef RSS
242  * a TCP packet turns up with a 2-tuple hash, or if an RSS hash is present but
243  * RSS is not compiled into the kernel.
249 #ifdef RSS
277 	 * RSS note: we pass foreign addr/port as source, and local addr/port
283 #ifdef RSS
291 #ifdef RSS
308 #ifdef	RSS
311 	 * RSS bucket and thus we should use this pcbgroup, rather than
369 #ifdef	RSS
431 		 * If the inp is an RSS bucket wildcard entry, ensure
462  * the hash on the mbuf to avoid doing a software hash calculation for RSS.