Network interface controller: Difference between revisions

Revision as of 11:26, 1 June 2023

Revision as of 01:18, 8 July 2023

Line 106:

| archive-url = https://web.archive.org/web/20150326095816/http://www.intel.com/content/dam/technology-provider/secure/us/en/documents/product-marketing-information/tst-grantley-launch-presentation-2014.pdf

| archive-date = March 26, 2015

}}</ref>{{rp|82}} Purely software implementations also exist, such as the [[receive packet steering]] (RPS) and [[receive flow steering]] (RFS).<ref name="linux-net-scaling" /> Further performance improvements can be achieved by routing the interrupt requests to the CPUs or cores executing the applications that are the ultimate destinations for [[network packet]]s that generated the interrupts. This technique improves [[Localitylocality of reference]] and results in higher overall performance, reduced latency and better hardware utilization because of the higher utilization of [[CPU cache]]s and fewer required [[context switch]]es. Examples of such implementations are the RFS<ref name="linux-net-scaling" /> and [[Intel]] ''Flow Director''.<ref name="intel-grantley" />{{rp|98,99}}<ref>{{cite web

| url = https://www.kernel.org/doc/Documentation/networking/ixgbe.txt

| title = Linux kernel documentation: Documentation/networking/ixgbe.txt