>> 2. How is the logic aware of RSS and RFS? >> >> With TCP sockets, the driver knows the specific ring it need to poll so >> this should be mapped and provide the best latency. > > > This code is blissfully oblivious of RFS and RSS, it only assumes that the > packets for a socket are likely to continue to come on the same queue. > The code is designed to be correct even if you get your data on the wrong > queue. (your performance will suffer but no more than that.) >
For low latency, you don't want to have to wait for the IPI that RPS sets to redirect packets to another CPU. However, this feature works extremely well with hardware flow steering (nfc/ntuple) and accelerated RFS, where the device will enqueue directly on an rxqueue owned exclusively by the destination cpu (if configured correctly). ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may _______________________________________________ E1000-devel mailing list E1000-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/e1000-devel To learn more about Intel® Ethernet, visit http://communities.intel.com/community/wired
