net: Add some clarification to skb_tx_timestamp() comment.
We've seen so many instances of people invoking skb_tx_timestamp() after the device already has been given the packet, that it's worth being a little bit more verbose and explicit in this comment. Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
37ec274e97
commit
73409f3b0f
|
@ -2531,6 +2531,10 @@ static inline void sw_tx_timestamp(struct sk_buff *skb)
|
||||||
* Ethernet MAC Drivers should call this function in their hard_xmit()
|
* Ethernet MAC Drivers should call this function in their hard_xmit()
|
||||||
* function immediately before giving the sk_buff to the MAC hardware.
|
* function immediately before giving the sk_buff to the MAC hardware.
|
||||||
*
|
*
|
||||||
|
* Specifically, one should make absolutely sure that this function is
|
||||||
|
* called before TX completion of this packet can trigger. Otherwise
|
||||||
|
* the packet could potentially already be freed.
|
||||||
|
*
|
||||||
* @skb: A socket buffer.
|
* @skb: A socket buffer.
|
||||||
*/
|
*/
|
||||||
static inline void skb_tx_timestamp(struct sk_buff *skb)
|
static inline void skb_tx_timestamp(struct sk_buff *skb)
|
||||||
|
|
Loading…
Reference in New Issue