From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Liming Sun <limings@nvidia.com>
Cc: Vadim Pasternak <vadimp@nvidia.com>,
David Thompson <davthompson@nvidia.com>,
Hans de Goede <hdegoede@redhat.com>,
Mark Gross <markgross@kernel.org>,
Dan Carpenter <dan.carpenter@linaro.org>,
platform-driver-x86@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3] Drop Tx network packet when Tx TmFIFO is full
Date: Fri, 12 Jan 2024 17:21:40 +0200 (EET) [thread overview]
Message-ID: <107b5fda-d3ec-48c1-107e-53502a1de0bd@linux.intel.com> (raw)
In-Reply-To: <20240111173106.96958-1-limings@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]
On Thu, 11 Jan 2024, Liming Sun wrote:
> Starting from Linux 5.16 kernel, Tx timeout mechanism was added
> in the virtio_net driver which prints the "Tx timeout" warning
> message when a packet stays in Tx queue for too long. Below is an
> example of the reported message:
>
> "[494105.316739] virtio_net virtio1 tmfifo_net0: TX timeout on
> queue: 0, sq: output.0, vq: 0×1, name: output.0, usecs since
> last trans: 3079892256".
>
> This issue could happen when external host driver which drains the
> FIFO is restared, stopped or upgraded. To avoid such confusing
> "Tx timeout" messages, this commit adds logic to drop the outstanding
> Tx packet if it's not able to transmit in two seconds due to Tx FIFO
> full, which can be considered as congestion or out-of-resource drop.
>
> This commit also handles the special case that the packet is half-
> transmitted into the Tx FIFO. In such case, the packet is discarded
> with remaining length stored in vring->rem_padding. So paddings with
> zeros can be sent out when Tx space is available to maintain the
> integrity of the packet format. The padded packet will be dropped on
> the receiving side.
>
> Signed-off-by: Liming Sun <limings@nvidia.com>
> ---
> v2->v3:
> Updates for Ilpo's comments:
> - Revises commit message to avoid confusion.
> v2: Fixed formatting warning
> v1: Initial version
Thanks, the commit message makes much more sense now!
Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
--
i.
next prev parent reply other threads:[~2024-01-12 15:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 15:04 [PATCH v1 1/1] Drop Tx network packet when Tx TmFIFO is full Liming Sun
2024-01-04 15:14 ` [PATCH v2 " Liming Sun
2024-01-04 17:38 ` Ilpo Järvinen
2024-01-05 17:40 ` Liming Sun
2024-01-08 14:23 ` Hans de Goede
2024-01-08 17:27 ` Liming Sun
2024-01-08 19:03 ` Ilpo Järvinen
2024-01-08 20:02 ` Liming Sun
2024-01-11 17:31 ` [PATCH v3] " Liming Sun
2024-01-12 15:21 ` Ilpo Järvinen [this message]
2024-01-22 11:24 ` Hans de Goede
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=107b5fda-d3ec-48c1-107e-53502a1de0bd@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=dan.carpenter@linaro.org \
--cc=davthompson@nvidia.com \
--cc=hdegoede@redhat.com \
--cc=limings@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=vadimp@nvidia.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