From: "naamax.meir" <naamax.meir@linux.intel.com>
To: Akihiko Odaki <akihiko.odaki@daynix.com>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Yuri Benditovich <yuri.benditovich@daynix.com>,
Eric Dumazet <edumazet@google.com>,
intel-wired-lan@lists.osuosl.org, Yan Vugenfirer <yan@daynix.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [Intel-wired-lan] [PATCH v2] e1000e: Fix TX dispatch condition
Date: Thu, 10 Nov 2022 11:55:25 +0200 [thread overview]
Message-ID: <03053677-059f-1ee9-436b-20846caddaa7@linux.intel.com> (raw)
In-Reply-To: <20221028130000.7318-1-akihiko.odaki@daynix.com>
On 10/28/2022 16:00, Akihiko Odaki wrote:
> e1000_xmit_frame is expected to stop the queue and dispatch frames to
> hardware if there is not sufficient space for the next frame in the
> buffer, but sometimes it failed to do so because the estimated maxmium
> size of frame was wrong. As the consequence, the later invocation of
> e1000_xmit_frame failed with NETDEV_TX_BUSY, and the frame in the buffer
> remained forever, resulting in a watchdog failure.
>
> This change fixes the estimated size by making it match with the
> condition for NETDEV_TX_BUSY. Apparently, the old estimation failed to
> account for the following lines which determines the space requirement
> for not causing NETDEV_TX_BUSY:
> ```
> /* reserve a descriptor for the offload context */
> if ((mss) || (skb->ip_summed == CHECKSUM_PARTIAL))
> count++;
> count++;
>
> count += DIV_ROUND_UP(len, adapter->tx_fifo_limit);
> ```
>
> This issue was found when running http-stress02 test included in Linux
> Test Project 20220930 on QEMU with the following commandline:
> ```
> qemu-system-x86_64 -M q35,accel=kvm -m 8G -smp 8
> -drive if=virtio,format=raw,file=root.img,file.locking=on
> -device e1000e,netdev=netdev
> -netdev tap,script=ifup,downscript=no,id=netdev
> ```
>
> Fixes: bc7f75fa9788 ("[E1000E]: New pci-express e1000 driver (currently for ICH9 devices only)")
> Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
> ---
> drivers/net/ethernet/intel/e1000e/netdev.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Tested-by: Naama Meir <naamax.meir@linux.intel.com>
prev parent reply other threads:[~2022-11-10 9:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-28 13:00 [PATCH v2] e1000e: Fix TX dispatch condition Akihiko Odaki
2022-11-03 16:16 ` [Intel-wired-lan] " G, GurucharanX
2022-11-10 9:55 ` naamax.meir [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=03053677-059f-1ee9-436b-20846caddaa7@linux.intel.com \
--to=naamax.meir@linux.intel.com \
--cc=akihiko.odaki@daynix.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pmenzel@molgen.mpg.de \
--cc=yan@daynix.com \
--cc=yuri.benditovich@daynix.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;
as well as URLs for NNTP newsgroup(s).