From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Vlad Yasevich <vyasevic@redhat.com>
Subject: Re: [PATCH net] macvtap: unbreak receiving of gro skb with frag list
Date: Mon, 26 Oct 2015 10:30:22 +0200 [thread overview]
Message-ID: <20151026102928-mutt-send-email-mst@redhat.com> (raw)
In-Reply-To: <562DCDF2.6030305@redhat.com>
On Mon, Oct 26, 2015 at 02:53:38PM +0800, Jason Wang wrote:
>
>
> On 10/26/2015 02:09 PM, Michael S. Tsirkin wrote:
> > On Mon, Oct 26, 2015 at 11:15:57AM +0800, Jason Wang wrote:
> >>
> >> On 10/23/2015 09:37 PM, Michael S. Tsirkin wrote:
> >>> On Fri, Oct 23, 2015 at 12:57:05AM -0400, Jason Wang wrote:
> >>>> We don't have fraglist support in TAP_FEATURES. This will lead
> >>>> software segmentation of gro skb with frag list. Fixes by having
> >>>> frag list support in TAP_FEATURES.
> >>>>
> >>>> With this patch single session of netperf receiving were restored from
> >>>> about 5Gb/s to about 12Gb/s on mlx4.
> >>>>
> >>>> Fixes a567dd6252 ("macvtap: simplify usage of tap_features")
> >>>> Cc: Vlad Yasevich <vyasevic@redhat.com>
> >>>> Cc: Michael S. Tsirkin <mst@redhat.com>
> >>>> Signed-off-by: Jason Wang <jasowang@redhat.com>
> >>> Thanks!
> >>> Does this mean we should look at re-adding NETIF_F_FRAGLIST
> >>> to virtio-net as well?
> >> Not sure I get the point, but probably not. This is for receiving and
> >> skb_copy_datagram_iter() can deal with frag list.
> >
> > Point is:
> > - bridge within guest
> > - assigned device creating gro skbs with frag list bridged to virtio
>
> I see, but this problem looks not specific to virtio. Most cards does
> not support frag list.
These will be slower when used with a bridge then, won't they?
--
MST
next prev parent reply other threads:[~2015-10-26 8:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 4:57 [PATCH net] macvtap: unbreak receiving of gro skb with frag list Jason Wang
2015-10-23 9:35 ` David Miller
2015-10-23 13:37 ` Michael S. Tsirkin
2015-10-26 3:15 ` Jason Wang
2015-10-26 6:09 ` Michael S. Tsirkin
2015-10-26 6:53 ` Jason Wang
2015-10-26 8:30 ` Michael S. Tsirkin [this message]
2015-10-27 2:58 ` Jason Wang
2015-10-27 9:05 ` Michael S. Tsirkin
2015-10-28 2:51 ` Jason Wang
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=20151026102928-mutt-send-email-mst@redhat.com \
--to=mst@redhat.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vyasevic@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.