Netdev List
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: felix.manlunas@cavium.com
Cc: netdev@vger.kernel.org, raghu.vatsavayi@cavium.com,
	derek.chickles@cavium.com, satananda.burla@cavium.com
Subject: Re: [PATCH V2 net-next] liquidio: prevent rx queues from getting stalled
Date: Fri, 30 Mar 2018 14:21:00 -0400 (EDT)	[thread overview]
Message-ID: <20180330.142100.1787650171524973056.davem@davemloft.net> (raw)
In-Reply-To: <20180329181322.GA9939@felix-thinkpad.cavium.com>

From: Felix Manlunas <felix.manlunas@cavium.com>
Date: Thu, 29 Mar 2018 11:13:22 -0700

> From: Raghu Vatsavayi <raghu.vatsavayi@cavium.com>
> 
> This commit has fix for RX traffic issues when we stress test the driver
> with continuous ifconfig up/down under very high traffic conditions.
> 
> Reason for the issue is that, in existing liquidio_stop function NAPI is
> disabled even before actual FW/HW interface is brought down via
> send_rx_ctrl_cmd(lio, 0). Between time frame of NAPI disable and actual
> interface down in firmware, firmware continuously enqueues rx traffic to
> host. When interrupt happens for new packets, host irq handler fails in
> scheduling NAPI as the NAPI is already disabled.
> 
> After "ifconfig <iface> up", Host re-enables NAPI but cannot schedule it
> until it receives another Rx interrupt. Host never receives Rx interrupt as
> it never cleared the Rx interrupt it received during interface down
> operation. NIC Rx interrupt gets cleared only when Host processes queue and
> clears the queue counts. Above anomaly leads to other issues like packet
> overflow in FW/HW queues, backpressure.
> 
> Fix:
> This commit fixes this issue by disabling NAPI only after informing
> firmware to stop queueing packets to host via send_rx_ctrl_cmd(lio, 0).
> send_rx_ctrl_cmd is not visible in the patch as it is already there in the
> code. The DOWN command also waits for any pending packets to be processed
> by NAPI so that the deadlock will not occur.
> 
> Signed-off-by: Raghu Vatsavayi <raghu.vatsavayi@cavium.com>
> Acked-by: Derek Chickles <derek.chickles@cavium.com>
> Signed-off-by: Felix Manlunas <felix.manlunas@cavium.com>

Applied.

      reply	other threads:[~2018-03-30 18:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-29 18:13 [PATCH V2 net-next] liquidio: prevent rx queues from getting stalled Felix Manlunas
2018-03-30 18:21 ` David Miller [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=20180330.142100.1787650171524973056.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=derek.chickles@cavium.com \
    --cc=felix.manlunas@cavium.com \
    --cc=netdev@vger.kernel.org \
    --cc=raghu.vatsavayi@cavium.com \
    --cc=satananda.burla@cavium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox