From: John Fastabend <john.r.fastabend@intel.com>
To: Vlad Yasevich <vyasevich@gmail.com>
Cc: nhorman@tuxdriver.com, alexander.h.duyck@intel.com,
netdev@vger.kernel.org, andy@greyhouse.net, davem@davemloft.net,
jeffrey.t.kirsher@intel.com
Subject: Re: [PATCH v2 0/2] l2 hardware accelerated macvlans
Date: Tue, 05 Nov 2013 07:17:21 -0800 [thread overview]
Message-ID: <52790C01.3070107@intel.com> (raw)
In-Reply-To: <5279051B.6000406@gmail.com>
On 11/5/2013 6:47 AM, Vlad Yasevich wrote:
> Hi John
>
[...]
>> series. It would be best (I think) to use the software
>> path for macvlan to macvlan traffic and save the PCIe
>> bus. Also this only allows for layer 2 mac forwarding
>> where some hardware supports more interesting forwarding
>> capabilities. Integrating with OVS may be useful here.
>
> This seems to be saying that for macvlan-macvlan
> case, you still prefere to do software based forwarding, but
> patch 1 in the series seem to always attempt to do hardware
> offloaded forwarding regardless of traffic and macvlan type.
> Can you clarify.
>
> Thanks
> -vlad
>
This series always attempts to do hardware offload even in the
macvlan-macvlan case as you note. I'm suggesting a further
optimization might be to use the software based forwarding in
this case. My plan is to investigate this after I get the initial
series completed.
.John
next prev parent reply other threads:[~2013-11-05 15:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-04 19:01 [PATCH v2 0/2] l2 hardware accelerated macvlans John Fastabend
2013-11-04 19:01 ` [PATCH v2 1/2] net: Add layer 2 hardware acceleration operations for macvlan devices John Fastabend
2013-11-05 14:15 ` Neil Horman
2013-11-04 19:01 ` [PATCH v2 2/2] ixgbe: enable l2 forwarding acceleration for macvlans John Fastabend
2013-11-05 6:24 ` John Fastabend
2013-11-05 14:26 ` Neil Horman
2013-11-05 20:34 ` John Fastabend
2013-11-05 20:52 ` Neil Horman
2013-11-05 14:47 ` [PATCH v2 0/2] l2 hardware accelerated macvlans Vlad Yasevich
2013-11-05 15:17 ` John Fastabend [this message]
2013-11-05 15:20 ` 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=52790C01.3070107@intel.com \
--to=john.r.fastabend@intel.com \
--cc=alexander.h.duyck@intel.com \
--cc=andy@greyhouse.net \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=vyasevich@gmail.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.