All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Fastabend <john.r.fastabend@intel.com>
To: vyasevic@redhat.com
Cc: nhorman@tuxdriver.com, davem@davemloft.net,
	alexander.h.duyck@intel.com, andy@greyhouse.net,
	netdev@vger.kernel.org, jeffrey.t.kirsher@intel.com,
	vyasevich@gmail.com
Subject: Re: [net-next PATCH v4 0/2] l2 hardware accelerated macvlans
Date: Mon, 11 Nov 2013 09:16:24 -0800	[thread overview]
Message-ID: <528110E8.8040708@intel.com> (raw)
In-Reply-To: <527C662B.4080300@redhat.com>

On 11/7/2013 8:18 PM, Vlad Yasevich wrote:

[...]

>> If folks find this series acceptable there are a few
>> items we can work on next. First broadcast and multicast
>> will use the hardware even for local traffic with this
>> series. It would be best (I think) to use the software
>> path for macvlan to macvlan traffic and save the PCIe
>> bus. This depends on how much you value CPU time vs
>> PCIE bandwidth. This will need another patch series
>> to flush out.
>>
>
> John
>
> So, I've been looking at these patches and the more I
> look the more I wonder how much benefit there is in
> sending unicast macvlan<->macvlan traffic through the hw.
> It looks like any bulk transfers would have to undergo
> tso segmentaion and GRO, where as this can be completely
> bypassed right now with software.
>
> Did you run any numbers?
>

I have run some numbers on previous versions of the code for
this. I'll take some new ones with the final code today/tomorrow
and post them.

Just wanted to let you know I saw this...

Thanks,
John

> Thanks
> -vlad
>
>

      reply	other threads:[~2013-11-11 17:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-06 17:54 [net-next PATCH v4 0/2] l2 hardware accelerated macvlans John Fastabend
2013-11-06 17:54 ` [net-next PATCH v4 1/2] net: Add layer 2 hardware acceleration operations for macvlan devices John Fastabend
2013-11-06 17:54 ` [net-next PATCH v4 2/2] ixgbe: enable l2 forwarding acceleration for macvlans John Fastabend
2013-11-08  0:12 ` [net-next PATCH v4 0/2] l2 hardware accelerated macvlans David Miller
2013-11-08  3:31   ` John Fastabend
2013-11-08  4:18 ` Vlad Yasevich
2013-11-11 17:16   ` John Fastabend [this message]

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=528110E8.8040708@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=vyasevic@redhat.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.