Searched hist:"84 f9307c5da84a7c8513e7607dc8427d2cbd63e3" (Results 1 – 2 of 2) sorted by relevance
| /openbmc/linux/include/net/ |
| H A D | flow.h | diff 84f9307c5da84a7c8513e7607dc8427d2cbd63e3 Wed Nov 30 13:00:53 CST 2011 Eric Dumazet <eric.dumazet@gmail.com> ipv4: use a 64bit load/store in output path
gcc compiler is smart enough to use a single load/store if we
memcpy(dptr, sptr, 8) on x86_64, regardless of
CONFIG_CC_OPTIMIZE_FOR_SIZE
In IP header, daddr immediately follows saddr, this wont change in the
future. We only need to make sure our flowi4 (saddr,daddr) fields wont
break the rule.
Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|
| /openbmc/linux/net/ipv4/ |
| H A D | ip_output.c | diff 84f9307c5da84a7c8513e7607dc8427d2cbd63e3 Wed Nov 30 13:00:53 CST 2011 Eric Dumazet <eric.dumazet@gmail.com> ipv4: use a 64bit load/store in output path
gcc compiler is smart enough to use a single load/store if we
memcpy(dptr, sptr, 8) on x86_64, regardless of
CONFIG_CC_OPTIMIZE_FOR_SIZE
In IP header, daddr immediately follows saddr, this wont change in the
future. We only need to make sure our flowi4 (saddr,daddr) fields wont
break the rule.
Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
|