All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Robert Hancock <robert.hancock@calian.com>
Cc: netdev@vger.kernel.org, radhey.shyam.pandey@xilinx.com,
	davem@davemloft.net
Subject: Re: [PATCH net 6/7] net: axienet: fix for TX busy handling
Date: Tue, 11 Jan 2022 19:49:48 -0800	[thread overview]
Message-ID: <20220111194948.056c7211@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net> (raw)
In-Reply-To: <20220111211358.2699350-7-robert.hancock@calian.com>

On Tue, 11 Jan 2022 15:13:57 -0600 Robert Hancock wrote:
> We should be avoiding returning NETDEV_TX_BUSY from ndo_start_xmit in
> normal cases. Move the main check for a full TX ring to the end of the
> function so that we stop the queue after the last available space is used
> up, and only wake up the queue if enough space is available for a full
> maximally fragmented packet. Print a warning if there is insufficient
> space at the start of start_xmit, since this should no longer happen.
> 
> Fixes: 8a3b7a252dca9 ("drivers/net/ethernet/xilinx: added Xilinx AXI Ethernet driver")
> Signed-off-by: Robert Hancock <robert.hancock@calian.com>

Feels a little more like an optimization than strictly a fix.
Can we apply this and the following patch to net-next in two
week's time? It's not too much of a stretch to take it in now
if it's a bit convenience but I don't think the Fixes tags should 
stay.

> -		netif_wake_queue(ndev);
> +		netdev_warn(ndev, "TX ring unexpectedly full\n");

Probably wise to make this netdev_warn_once() or at least rate limit it.

> +		return NETDEV_TX_BUSY;
>  	}
>  
>  	if (skb->ip_summed == CHECKSUM_PARTIAL) {


  reply	other threads:[~2022-01-12  3:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11 21:13 [PATCH net 0/7] Xilinx axienet fixes Robert Hancock
2022-01-11 21:13 ` [PATCH net 1/7] net: axienet: Reset core before accessing MAC and wait for core ready Robert Hancock
2022-01-12  0:30   ` Robert Hancock
2022-01-12  3:24     ` Jakub Kicinski
2022-01-12 16:46       ` Robert Hancock
2022-01-11 21:13 ` [PATCH net 2/7] net: axienet: add missing memory barriers Robert Hancock
2022-01-11 21:13 ` [PATCH net 3/7] net: axienet: limit minimum TX ring size Robert Hancock
2022-01-11 21:13 ` [PATCH net 4/7] net: axienet: Fix TX ring slot available check Robert Hancock
2022-01-11 21:13 ` [PATCH net 5/7] net: axienet: fix number of TX ring slots for " Robert Hancock
2022-01-11 21:13 ` [PATCH net 6/7] net: axienet: fix for TX busy handling Robert Hancock
2022-01-12  3:49   ` Jakub Kicinski [this message]
2022-01-12 16:45     ` Robert Hancock
2022-01-12 17:01       ` Jakub Kicinski
2022-01-12 17:35         ` Robert Hancock
2022-01-11 21:13 ` [PATCH net 7/7] net: axienet: increase default TX ring size to 128 Robert Hancock

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=20220111194948.056c7211@kicinski-fedora-PC1C0HJN.hsd1.ca.comcast.net \
    --to=kuba@kernel.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=radhey.shyam.pandey@xilinx.com \
    --cc=robert.hancock@calian.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.