[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <44770d6b-503c-279f-807f-0b7f11be56cf@gmail.com>
Date: Wed, 27 Jun 2018 16:56:27 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Jesus Sanchez-Palencia <jesus.sanchez-palencia@...el.com>,
netdev@...r.kernel.org
Cc: tglx@...utronix.de, jan.altenberg@...utronix.de,
vinicius.gomes@...el.com, kurt.kanzenbach@...utronix.de,
henrik@...tad.us, richardcochran@...il.com,
levi.pearson@...man.com, ilias.apalodimas@...aro.org,
ivan.khoronzhuk@...aro.org, mlichvar@...hat.com,
willemb@...gle.com, jhs@...atatu.com, xiyou.wangcong@...il.com,
jiri@...nulli.us
Subject: Re: [PATCH v1 net-next 12/14] igb: Only call skb_tx_timestamp after
descriptors are ready
On 06/27/2018 02:59 PM, Jesus Sanchez-Palencia wrote:
> Currently, skb_tx_timestamp() is being called before the DMA
> descriptors are prepared in igb_xmit_frame_ring(), which happens
> during either the igb_tso() or igb_tx_csum() calls.
>
> Given that now the skb->tstamp might be used to carry the timestamp
> for SO_TXTIME, we must only call skb_tx_timestamp() after the
> information has been copied into the DMA tx_ring.
Since when this skb->tstamp use happened ?
If this is in patch 11/14 (igb: Add support for ETF offload), then you should either :
1) Squash this into 11/14
2) swap 11 and 12 patch, so that this change is done before "igb: Add support for ETF offload"
Otherwise a bisection could fail badly.
Powered by blists - more mailing lists