From: Ben Greear <greearb@candelatech.com>
To: Vlad Yasevich <vyasevic@redhat.com>
Cc: netdev@vger.kernel.org, Florian Westphal <fw@strlen.de>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Jason Wang <jasowang@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH v2 net] macvlan: Add support for 'always_on' offload features
Date: Mon, 03 Mar 2014 15:49:40 -0800 [thread overview]
Message-ID: <53151514.4080906@candelatech.com> (raw)
In-Reply-To: <1393878833-17667-1-git-send-email-vyasevic@redhat.com>
On 03/03/2014 12:33 PM, Vlad Yasevich wrote:
> Macvlan currently inherits all of its features from the lower
> device. When lower device disables offload support, this causes
> macvlan to disable offload support as well. This causes
> performance regression when using macvlan/macvtap in bridge
> mode.
>
> It can be easily demonstrated by creating 2 namespaces using
> macvlan in bridge mode and running netperf between them:
>
> MIGRATED TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 10.0.0.1 () port 0 AF_INET
> Recv Send Send
> Socket Socket Message Elapsed
> Size Size Size Time Throughput
> bytes bytes bytes secs. 10^6bits/sec
>
> 87380 16384 16384 20.00 1204.61
>
> To restore the performance, we add software offload features
> to the list of "always_on" features for macvlan. This way
> when a namespace or a guest using macvtap initially sends a
> packet, this packet will not be segmented at macvlan level.
> It will only be segmented when macvlan sends the packet
> to the lower device.
If users specifically disable the offload features on the macvlan using ethtool,
will they be turned off? If not, then I think that logic should
be kept somehow?
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2014-03-03 23:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 20:33 [PATCH v2 net] macvlan: Add support for 'always_on' offload features Vlad Yasevich
2014-03-03 21:44 ` David Miller
2014-03-03 23:49 ` Ben Greear [this message]
2014-03-04 13:44 ` Vlad Yasevich
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=53151514.4080906@candelatech.com \
--to=greearb@candelatech.com \
--cc=borntraeger@de.ibm.com \
--cc=fw@strlen.de \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--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 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).