• S
    [AF_PACKET]: Don't enable global timestamps. · 50f17787
    Stephen Hemminger 提交于
    Andi mentioned he did something like this already, but never submitted
    it.
    
    The dhcp client application uses AF_PACKET with a packet filter to
    receive data. The application doesn't even use timestamps, but because
    the AF_PACKET API has timestamps, they get turned on globally which
    causes an expensive time of day lookup for every packet received on
    any system that uses the standard DHCP client.
    
    The fix is to not enable the timestamp (but use if if available).
    This causes the time lookup to only occur on those packets that are
    destined for the AF_PACKET socket.  The timestamping occurs after
    packet filtering so all packets dropped by filtering to not cause a
    clock call.
    
    The one downside of this a a few microseconds additional delay added
    from the normal timestamping location (netif_rx) until the receive
    callback in AF_PACKET. But since the offset is fairly consistent it
    should not upset applications that do want really use timestamps, like
    wireshark.
    Signed-off-by: NStephen Hemminger <shemminger@linux-foundation.org>
    Signed-off-by: NDavid S. Miller <davem@davemloft.net>
    50f17787
af_packet.c 43.2 KB