From: Eric Dumazet <eric.dumazet@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
Dave Taht <dave.taht@gmail.com>
Cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Xianting Tian <xianting.tian@linux.alibaba.com>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
virtualization <virtualization@lists.linux-foundation.org>,
bloat <bloat@lists.bufferbloat.net>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [Bloat] virtio_net: BQL?
Date: Wed, 19 May 2021 16:31:10 +0200 [thread overview]
Message-ID: <a11eee78-b2a1-3dbc-4821-b5f4bfaae819@gmail.com> (raw)
In-Reply-To: <20210517160036.4093d3f2@hermes.local>
On 5/18/21 1:00 AM, Stephen Hemminger wrote:
>
> The Azure network driver (netvsc) also does not have BQL. Several years ago
> I tried adding it but it benchmarked worse and there is the added complexity
> of handling the accelerated networking VF path.
>
Note that NIC with many TX queues make BQL almost useless, only adding extra
overhead.
We should probably make BQL something that can be manually turned on/off.
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2021-05-19 14:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <56270996-33a6-d71b-d935-452dad121df7@linux.alibaba.com>
2021-05-17 14:35 ` [PATCH] virtio_net: Use BUG_ON instead of if condition followed by BUG Andrew Lunn
[not found] ` <CAA93jw6LUAnWZj0b5FvefpDKUyd6cajCNLoJ6OKrwbu-V_ffrA@mail.gmail.com>
2021-05-17 20:23 ` virtio_net: BQL? Willem de Bruijn
[not found] ` <CAA93jw7Vr_pFMsPCrPadqaLGu0BdC-wtCmW2iyHFkHERkaiyWQ@mail.gmail.com>
[not found] ` <20210517160036.4093d3f2@hermes.local>
2021-05-19 14:31 ` Eric Dumazet [this message]
2021-05-24 2:53 ` Jason Wang
2021-05-24 9:10 ` Michael S. Tsirkin
2021-05-19 8:35 ` Michael S. Tsirkin
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=a11eee78-b2a1-3dbc-4821-b5f4bfaae819@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=willemdebruijn.kernel@gmail.com \
--cc=xianting.tian@linux.alibaba.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).