All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Claudiu.Beznea@microchip.com>
To: <Nicolas.Ferre@microchip.com>, <anssi.hannula@bitwise.fi>,
	<davem@davemloft.net>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH 0/3] net: macb: DMA race condition fixes
Date: Mon, 10 Dec 2018 11:32:04 +0000	[thread overview]
Message-ID: <284d5c20-7acd-625f-cabc-b1ba0a7f3136@microchip.com> (raw)
In-Reply-To: <049619f8-e629-ca59-bed4-85eea49dd29a@microchip.com>



On 10.12.2018 12:58, Nicolas Ferre - M43238 wrote:
> On 07/12/2018 at 13:04, Anssi Hannula wrote:
>> On 5.12.2018 22:35, David Miller wrote:
>>> From: Anssi Hannula <anssi.hannula@bitwise.fi>
>>> Date: Fri, 30 Nov 2018 20:21:34 +0200
>>>
>>>> Here are a couple of race condition fixes for the macb driver. The first
>>>> two are issues observed on real HW.
>>> It looks like there is still an active discussion about the memory
>>> barriers in patch #3 being excessive.
>>>
>>> Once that is sorted out to everyone's satisfaction, would you
>>> please repost this series with appropriate ACKs, reviewed-by's,
>>> tested-by's, etc. added?
>>>
>>> Thank you.
>>
>>
>> OK, I'll do that once everything is sorted.
>>
>> Nicolas, were Claudiu's tests the ones you wanted to wait for or are we
>> waiting for more tests?
> 
> Claudiu will report on our tests. The discussion is still progress from 
> what I can tell. Thanks a lot for continuing in participating to this 
> thread!

As I said, I tested this series on heavy traffic load and in the setup we
observed the issue with TX used bit read interrupt (see patch "net: macb:
restart tx after tx used bit read" I submitted these days) on our SAMA5D2
Xplained and SAMA5D4 Xplained boards. With patches 1 & 2 from this series I
can say the "not whole frame pointed by descriptor" issue is not present
anymore.

The idea with tests was to see if this series has any impact on "tx used
bit read" issue we faced with. The result is no, the "net: macb: restart tx
after tx used bit read" patch is needed. I asked for postponing of this to
run more tests on my side (independent of this series with memory barriers).

Thank you,
Claudiu Beznea

> 
> Best regards,
> 

  reply	other threads:[~2018-12-10 11:32 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-30 18:21 [PATCH 0/3] net: macb: DMA race condition fixes Anssi Hannula
2018-11-30 18:21 ` [PATCH 1/3] net: macb: fix random memory corruption on RX with 64-bit DMA Anssi Hannula
2018-12-03  4:44   ` Harini Katakam
2018-12-05 12:37   ` Claudiu.Beznea
2018-12-05 13:58     ` Anssi Hannula
2018-12-05 20:32   ` David Miller
2018-12-06 14:16     ` Claudiu.Beznea
2018-11-30 18:21 ` [PATCH 2/3] net: macb: fix dropped RX frames due to a race Anssi Hannula
2018-12-03  4:52   ` Harini Katakam
2018-12-03 10:31     ` Anssi Hannula
2018-12-03 10:36       ` Harini Katakam
2018-12-05 12:38   ` Claudiu.Beznea
2018-11-30 18:21 ` [PATCH 3/3] net: macb: add missing barriers when reading buffers Anssi Hannula
2018-12-05 12:37   ` Claudiu.Beznea
2018-12-05 14:00     ` Anssi Hannula
2018-12-06 14:14       ` Claudiu.Beznea
2018-12-07 12:00         ` Anssi Hannula
2018-12-10 10:34           ` Claudiu.Beznea
2018-12-11 13:21             ` Anssi Hannula
2018-12-12 10:58               ` Claudiu.Beznea
2018-12-12 11:27                 ` Anssi Hannula
2018-12-13 10:48                   ` Claudiu.Beznea
2018-12-12 10:59               ` [PATCH 3/3 v2] net: macb: add missing barriers when reading descriptors Anssi Hannula
2018-12-12 23:19                 ` David Miller
2018-12-03  8:26 ` [PATCH 0/3] net: macb: DMA race condition fixes Nicolas.Ferre
2018-12-03 23:56   ` David Miller
2018-12-05 20:35 ` David Miller
2018-12-07 12:04   ` Anssi Hannula
2018-12-10 10:58     ` Nicolas.Ferre
2018-12-10 11:32       ` Claudiu.Beznea [this message]
2018-12-10 11:34         ` Claudiu.Beznea

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=284d5c20-7acd-625f-cabc-b1ba0a7f3136@microchip.com \
    --to=claudiu.beznea@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=anssi.hannula@bitwise.fi \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.