RE: [PATCH v2 1/2] net: nps_enet: Sync access to packet sent flag

From: Elad Kanfi
Date: Mon May 02 2016 - 06:55:44 EST

-----Original Message-----
From: David Miller [mailto:davem@xxxxxxxxxxxxx]
Sent: Friday, April 29, 2016 12:11 AM
To: Elad Kanfi
Cc: Noam Camus; linux-kernel@xxxxxxxxxxxxxxx; abrodkin@xxxxxxxxxxxx; Tal Zilcer; netdev@xxxxxxxxxxxxxxx
Subject: Re: [PATCH v2 1/2] net: nps_enet: Sync access to packet sent flag

From: Elad Kanfi <eladkan@xxxxxxxxxxxx>
Date: Wed, 27 Apr 2016 16:18:29 +0300

> From: Elad Kanfi <eladkan@xxxxxxxxxxxx>
> Below is a description of a possible problematic sequence. CPU-A is
> sending a frame and CPU-B handles the interrupt that indicates the
> frame was sent. CPU-B reads an invalid value of tx_packet_sent.
> ----- -----
> nps_enet_send_frame
> .
> .
> tx_packet_sent = true
> order HW to start tx
> .
> .
> HW complete tx
> ------> get tx complete interrupt
> .
> .
> if(tx_packet_sent == true)
> end memory transaction
> (tx_packet_sent actually
> written)
> Problem solution:
> Add a memory barrier after setting tx_packet_sent, in order to make
> sure that it is written before the packet is sent.
> Signed-off-by: Elad Kanfi <eladkan@xxxxxxxxxxxx>
> Acked-by: Noam Camus <noamca@xxxxxxxxxxxx>
> Please address the feedback about memory barrier pairing.
> Also, for both patches, do not put empty lines between the various tags at the end of the commit message. They should all be together in one continuous group.

Since this driver handles one frame at a time, I couldn't find a case that requires the paired barrier.

The order of reads is not critical once it is assured that the value is valid.

If there is something I'm missing or for the sake of good order, I can add it.

Please let me know your opinion on this.

I will remove the empty lines in the commit messages at the next patches version.