From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, nhorman@redhat.com, sassmann@redhat.com,
jogreene@redhat.com
Subject: Re: [net-next 00/10][pull request] 10GbE Intel Wired LAN Driver Updates 2018-04-25
Date: Wed, 25 Apr 2018 15:18:43 -0400 (EDT) [thread overview]
Message-ID: <20180425.151843.495629824032757479.davem@davemloft.net> (raw)
In-Reply-To: <20180425153305.25878-1-jeffrey.t.kirsher@intel.com>
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Wed, 25 Apr 2018 08:32:55 -0700
> This series represents yet another phase of the macvlan cleanup Alex has
> been working on.
>
> The main goal of these changes is to make it so that we only support
> offloading what we can actually offload and we don't break any existing
> functionality. So for example we were claiming to advertise source mode
> macvlan and we were doing nothing of the sort, so support for that has been
> dropped.
>
> The biggest change with this set is that broadcast/multicast replication is
> no longer being supported in software. Alex dropped it as it leads to
> scaling issues when a broadcast frame has to be replicated up to 64 times.
>
> Beyond that this set goes through and optimized the time needed to bring up
> and tear down the macvlan interfaces on ixgbe and provides a clean way for
> us to disable the macvlan offload when needed.
Ok, the macvlan changes look good to me.
> The following are changes since commit c749fa181bd5848be78691d23168ec61ce691b95:
> Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net
> and are available in the git repository at:
> git://git.kernel.org/pub/scm/linux/kernel/git/jkirsher/next-queue 10GbE
I'll pull this into net-next, thanks everyone.
prev parent reply other threads:[~2018-04-25 19:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 15:32 [net-next 00/10][pull request] 10GbE Intel Wired LAN Driver Updates 2018-04-25 Jeff Kirsher
2018-04-25 15:32 ` [net-next 01/10] ixgbe: Drop support for macvlan specific unicast lists Jeff Kirsher
2018-04-25 15:32 ` [net-next 02/10] macvlan: Rename fwd_priv to accel_priv and add accessor function Jeff Kirsher
2018-04-25 15:32 ` [net-next 03/10] macvlan: Use software path for offloaded local, broadcast, and multicast traffic Jeff Kirsher
2018-04-25 15:32 ` [net-next 04/10] ixgbe/fm10k: Drop tracking stats for macvlan broadcast/multicast Jeff Kirsher
2018-04-25 15:33 ` [net-next 05/10] macvlan: macvlan_count_rx shouldn't be static inline AND extern Jeff Kirsher
2018-04-25 15:33 ` [net-next 06/10] macvlan: Add function to test for destination filtering support Jeff Kirsher
2018-04-25 15:33 ` [net-next 07/10] macvlan: Provide function for interfaces to release HW offload Jeff Kirsher
2018-04-25 15:33 ` [net-next 08/10] ixgbe/fm10k: Only support macvlan offload for types that support destination filtering Jeff Kirsher
2018-04-25 15:33 ` [net-next 09/10] ixgbe: Drop real_adapter from l2 fwd acceleration structure Jeff Kirsher
2018-04-25 15:33 ` [net-next 10/10] ixgbe: Avoid performing unnecessary resets for macvlan offload Jeff Kirsher
2018-04-25 19:18 ` David Miller [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=20180425.151843.495629824032757479.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jogreene@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@redhat.com \
--cc=sassmann@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).