From: Maciej Fijalkowski <maciej.fijalkowski@intel.com>
To: sven.auhagen@voleatech.de
Cc: anthony.l.nguyen@intel.com, davem@davemloft.net,
netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
sandeep.penigalapati@intel.com, brouer@redhat.com
Subject: Re: [PATCH 7/7] igb: avoid transmit queue timeout in xdp path
Date: Wed, 7 Oct 2020 23:35:49 +0200 [thread overview]
Message-ID: <20201007213549.GF48010@ranger.igk.intel.com> (raw)
In-Reply-To: <20201007152506.66217-8-sven.auhagen@voleatech.de>
On Wed, Oct 07, 2020 at 05:25:06PM +0200, sven.auhagen@voleatech.de wrote:
> From: Sven Auhagen <sven.auhagen@voleatech.de>
>
> Since we share the transmit queue with the slow path,
> it is possible that we run into a transmit queue timeout.
> This will reset the queue.
> This happens under high load when the fast path is using the
> transmit queue pretty much exclusively.
Please mention in the commit message *how* you are fixing this issue.
>
> Signed-off-by: Sven Auhagen <sven.auhagen@voleatech.de>
> ---
> drivers/net/ethernet/intel/igb/igb_main.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/net/ethernet/intel/igb/igb_main.c b/drivers/net/ethernet/intel/igb/igb_main.c
> index 6a2828b96eef..d84a99359e95 100644
> --- a/drivers/net/ethernet/intel/igb/igb_main.c
> +++ b/drivers/net/ethernet/intel/igb/igb_main.c
> @@ -2916,6 +2916,8 @@ static int igb_xdp_xmit_back(struct igb_adapter *adapter, struct xdp_buff *xdp)
>
> nq = txring_txq(tx_ring);
> __netif_tx_lock(nq, cpu);
> + /* Avoid transmit queue timeout since we share it with the slow path */
> + nq->trans_start = jiffies;
> ret = igb_xmit_xdp_ring(adapter, tx_ring, xdpf);
> __netif_tx_unlock(nq);
>
> @@ -2948,6 +2950,9 @@ static int igb_xdp_xmit(struct net_device *dev, int n,
> nq = txring_txq(tx_ring);
> __netif_tx_lock(nq, cpu);
>
> + /* Avoid transmit queue timeout since we share it with the slow path */
> + nq->trans_start = jiffies;
> +
> for (i = 0; i < n; i++) {
> struct xdp_frame *xdpf = frames[i];
> int err;
> --
> 2.20.1
>
prev parent reply other threads:[~2020-10-07 21:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 15:24 [PATCH 0/7] igb: xdp patches followup sven.auhagen
2020-10-07 15:25 ` [PATCH 1/7] igb: XDP xmit back fix error code sven.auhagen
2020-10-07 15:25 ` [PATCH 2/7] igb: take vlan double header into account sven.auhagen
2020-10-07 21:06 ` Maciej Fijalkowski
2020-10-08 5:25 ` Sven Auhagen
2020-10-07 15:25 ` [PATCH 3/7] igb: XDP extack message on error sven.auhagen
2020-10-07 21:08 ` Maciej Fijalkowski
2020-10-07 15:25 ` [PATCH 4/7] igb: skb add metasize for xdp sven.auhagen
2020-10-07 21:10 ` Maciej Fijalkowski
2020-10-07 15:25 ` [PATCH 5/7] igb: use igb_rx_buffer_flip sven.auhagen
2020-10-07 21:32 ` Maciej Fijalkowski
2020-10-08 5:29 ` Sven Auhagen
2020-10-07 15:25 ` [PATCH 6/7] igb: use xdp_do_flush sven.auhagen
2020-10-07 21:34 ` Maciej Fijalkowski
2020-10-07 15:25 ` [PATCH 7/7] igb: avoid transmit queue timeout in xdp path sven.auhagen
2020-10-07 21:35 ` Maciej Fijalkowski [this message]
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=20201007213549.GF48010@ranger.igk.intel.com \
--to=maciej.fijalkowski@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=brouer@redhat.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sandeep.penigalapati@intel.com \
--cc=sassmann@redhat.com \
--cc=sven.auhagen@voleatech.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).