From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: "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>,
Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: virtio_net: BQL?
Date: Mon, 17 May 2021 16:23:10 -0400 [thread overview]
Message-ID: <CA+FuTSf0Af2RXEG=rCthNNEb5mwKTG37gpEBBZU16qKkvmF=qw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6LUAnWZj0b5FvefpDKUyd6cajCNLoJ6OKrwbu-V_ffrA@mail.gmail.com>
On Mon, May 17, 2021 at 2:44 PM Dave Taht <dave.taht@gmail.com> wrote:
>
> Not really related to this patch, but is there some reason why virtio
> has no support for BQL?
There have been a few attempts to add it over the years.
Most recently, https://lore.kernel.org/lkml/20181205225323.12555-2-mst@redhat.com/
That thread has a long discussion. I think the key open issue remains
"The tricky part is the mode switching between napi and no napi."
> On Mon, May 17, 2021 at 11:41 AM Xianting Tian
> <xianting.tian@linux.alibaba.com> wrote:
> >
> > BUG_ON() uses unlikely in if(), which can be optimized at compile time.
> >
> > Signed-off-by: Xianting Tian <xianting.tian@linux.alibaba.com>
> > ---
> > drivers/net/virtio_net.c | 5 ++---
> > 1 file changed, 2 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
> > index c921ebf3ae82..212d52204884 100644
> > --- a/drivers/net/virtio_net.c
> > +++ b/drivers/net/virtio_net.c
> > @@ -1646,10 +1646,9 @@ static int xmit_skb(struct send_queue *sq, struct
> > sk_buff *skb)
> > else
> > hdr = skb_vnet_hdr(skb);
> >
> > - if (virtio_net_hdr_from_skb(skb, &hdr->hdr,
> > + BUG_ON(virtio_net_hdr_from_skb(skb, &hdr->hdr,
> > virtio_is_little_endian(vi->vdev), false,
> > - 0))
> > - BUG();
> > + 0));
> >
> > if (vi->mergeable_rx_bufs)
> > hdr->num_buffers = 0;
> > --
> > 2.17.1
> >
>
>
> --
> Latest Podcast:
> https://www.linkedin.com/feed/update/urn:li:activity:6791014284936785920/
>
> Dave Täht CTO, TekLibre, LLC
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2021-05-17 20:23 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 ` Willem de Bruijn [this message]
[not found] ` <CAA93jw7Vr_pFMsPCrPadqaLGu0BdC-wtCmW2iyHFkHERkaiyWQ@mail.gmail.com>
[not found] ` <20210517160036.4093d3f2@hermes.local>
2021-05-19 14:31 ` [Bloat] virtio_net: BQL? Eric Dumazet
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='CA+FuTSf0Af2RXEG=rCthNNEb5mwKTG37gpEBBZU16qKkvmF=qw@mail.gmail.com' \
--to=willemdebruijn.kernel@gmail.com \
--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=virtualization@lists.linux-foundation.org \
--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).