All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: Ingo Rohloff <ingo.rohloff@lauterbach.com>, <robert.hancock@calian.com>
Cc: <Nicolas.Ferre@microchip.com>, <claudiu.beznea@microchip.com>,
	<davem@davemloft.net>, <kuba@kernel.org>,
	<netdev@vger.kernel.org>, <tomas.melin@vaisala.com>
Subject: Re: [PATCH 1/1] net: macb: A different way to restart a stuck TX descriptor ring.
Date: Tue, 11 Apr 2023 08:25:08 -0700	[thread overview]
Message-ID: <5cd0369c-4bd6-e5bb-c2a2-04be52ebaa72@intel.com> (raw)
In-Reply-To: <20230407213349.8013-2-ingo.rohloff@lauterbach.com>

On 4/7/2023 2:33 PM, Ingo Rohloff wrote:
> This implements a different approach than Commit 4298388574dae6 ("net:
> macb: restart tx after tx used bit read"):
> 
> When reaping TX descriptors in macb_tx_complete(), if there are still
> active descriptors pending (queue is not empty) and the controller
> additionally signals that it is not any longer working on the TX ring,
> then something has to be wrong. Reasoning:
> Each time a descriptor is added to the TX ring (via macb_start_xmit()) the
> controller is triggered to start transmitting (via setting the TSTART
> bit).
> At this point in time, there are two cases:
> 1) The controller already has read an inactive descriptor
>    (with a set TX_USED bit).
> 2) The controller has not yet read an inactive descriptor
>    and is still actively transmitting.
> 
> In case 1) setting the TSTART bit, should restart transmission.
> In case 2) the controller should continue transmitting and at some point
> reach the freshly added descriptors and then process them too.
> 
> This patch checks in macb_tx_complete() if the TX queue is non-empty and
> additionally if the controller indicates that it is not transmitting any
> longer. If this condition is detected, the TSTART bit is set again to
> restart transmission.
> 
> Signed-off-by: Ingo Rohloff <ingo.rohloff@lauterbach.com>


I see this series is still under discussion. Next time you send please
use correct subject line:
[PATCH net v1] macb: ...

Also please be sure to cc the correct maintainers.


  reply	other threads:[~2023-04-11 15:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-17 10:02 [PATCH v3] net: macb: restart tx after tx used bit read Claudiu.Beznea
2018-12-17 10:14 ` Nicolas.Ferre
2018-12-18 23:58 ` David Miller
2022-03-23  8:08 ` Tomas Melin
2022-03-23 15:43   ` Jakub Kicinski
2022-03-23 16:42     ` Robert Hancock
2022-03-25  7:10       ` Tomas Melin
2022-03-25  8:13       ` Claudiu.Beznea
2022-03-25  9:33         ` Tomas Melin
2023-04-07 21:33       ` [PATCH 0/1] Alternative, " Ingo Rohloff
2023-04-07 21:33         ` [PATCH 1/1] net: macb: A different way to restart a stuck TX descriptor ring Ingo Rohloff
2023-04-11 15:25           ` Jesse Brandeburg [this message]
2023-04-10 17:05         ` [PATCH 0/1] Alternative, restart tx after tx used bit read Robert Hancock
2023-04-12  2:07         ` Jakub Kicinski
2023-04-12  3:17           ` Lars-Peter Clausen
2023-04-12  3:43           ` Roman Gushchin
2023-04-21 13:00           ` [PATCH v2 0/1] net: macb: Avoid erroneously stopped TX ring Ingo Rohloff
2023-04-21 13:00           ` [PATCH v2 1/1] " Ingo Rohloff
2023-04-22  2:57             ` Jakub Kicinski
2023-04-12  6:27         ` [PATCH 0/1] Alternative, restart tx after tx used bit read Tomas Melin
2023-04-12 16:17           ` Robert Hancock
2023-04-24  8:54         ` 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=5cd0369c-4bd6-e5bb-c2a2-04be52ebaa72@intel.com \
    --to=jesse.brandeburg@intel.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=claudiu.beznea@microchip.com \
    --cc=davem@davemloft.net \
    --cc=ingo.rohloff@lauterbach.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=robert.hancock@calian.com \
    --cc=tomas.melin@vaisala.com \
    /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.