Searched hist:164901 (Results 1 - 6 of 6) sorted by relevance
/freebsd-10.2-release/sys/dev/iicbus/ | ||
H A D | iicbus_if.m | diff 164901 Tue Dec 05 06:19:36 MST 2006 imp const poison submitted by: john wehle |
H A D | iiconf.h | diff 164901 Tue Dec 05 06:19:36 MST 2006 imp const poison submitted by: john wehle |
H A D | iiconf.c | diff 164901 Tue Dec 05 06:19:36 MST 2006 imp const poison submitted by: john wehle |
/freebsd-10.2-release/sys/net/ | ||
H A D | if_lagg.h | diff 232008 Wed Feb 22 22:04:28 MST 2012 thompsa Using the flowid in the mbuf assumes the network card is giving a good hash for the traffic flow, this may not be the case giving poor traffic distribution. Add a sysctl which allows us to fall back to our own flow hash code. PR: kern/164901 Submitted by: Eugene Grosbein MFC after: 1 week |
H A D | ieee8023ad_lacp.c | diff 232008 Wed Feb 22 22:04:28 MST 2012 thompsa Using the flowid in the mbuf assumes the network card is giving a good hash for the traffic flow, this may not be the case giving poor traffic distribution. Add a sysctl which allows us to fall back to our own flow hash code. PR: kern/164901 Submitted by: Eugene Grosbein MFC after: 1 week |
H A D | if_lagg.c | diff 232008 Wed Feb 22 22:04:28 MST 2012 thompsa Using the flowid in the mbuf assumes the network card is giving a good hash for the traffic flow, this may not be the case giving poor traffic distribution. Add a sysctl which allows us to fall back to our own flow hash code. PR: kern/164901 Submitted by: Eugene Grosbein MFC after: 1 week |
Completed in 97 milliseconds