netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Fastabend <john.fastabend@gmail.com>
To: roopa@cumulusnetworks.com
Cc: sfeldma@gmail.com, jiri@resnulli.us, netdev@vger.kernel.org,
	davem@davemloft.net
Subject: Re: [PATCH net-next] rocker: check for BRIDGE_FLAGS_SELF in bridge setlink handler
Date: Tue, 03 Mar 2015 20:15:46 -0800	[thread overview]
Message-ID: <54F686F2.5010404@gmail.com> (raw)
In-Reply-To: <1425428129-48365-1-git-send-email-roopa@cumulusnetworks.com>

On 03/03/2015 04:15 PM, roopa@cumulusnetworks.com wrote:
> From: Roopa Prabhu <roopa@cumulusnetworks.com>
>
> With the recent addition of the NETIF_F_HW_SWITCH_OFFLOAD flag
> on rocker ports, the second command (bridge link set) below will turn off
> learning in the rocker hw (Scott/Jiri, need some confirmation from
> you that this is indeed a problem and if the below patch is ok).
>
> ip link set dev swp1 master br0
> bridge link set dev swp1 learning off master
> bridge link set dev swp1 learning_sync on self
>
> This patch fixes rocker to ignore learning setting when 'master'
> is set. This makes it possible to set/unset learning in kernel and bridge
> driver independently.
>
> The below command will continue to set learning on in both kernel and rocker
> hw:
> bridge link set dev swp1 learning on
>
> Signed-off-by: Roopa Prabhu <roopa@cumulusnetworks.com>
> ---

We will at least want this behaviour in the NIC case where the NIC
can support l2 learning and forwarding to VF's or even other ports.
(remind again when a NIC becomes a switch and a switch becomes a NIC?).

In this case you may want to learn in the hardware but in the
hypervisor only support assigned MAC address because this is
controlled by a libvirt/qemu for example.

.John

-- 
John Fastabend         Intel Corporation

  reply	other threads:[~2015-03-04  4:15 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-04  0:15 [PATCH net-next] rocker: check for BRIDGE_FLAGS_SELF in bridge setlink handler roopa
2015-03-04  4:15 ` John Fastabend [this message]
2015-03-04  7:02 ` Scott Feldman
2015-03-04  8:51   ` roopa
2015-03-04 16:24     ` Scott Feldman
2015-03-05  0:31       ` roopa
2015-03-05  8:02     ` Jiri Pirko
2015-03-05 14:55       ` roopa
2015-03-05 20:06         ` Scott Feldman
2015-03-05 20:43           ` roopa
2015-03-05 21:40             ` roopa
2015-03-06  9:52             ` Scott Feldman
2015-03-08 14:19               ` roopa
2015-03-08 23:17                 ` Scott Feldman
2015-03-09  0:20                   ` roopa
     [not found]                   ` <CAJieiUhHdXOZjWkb4s_GviLwzq5Gct-1o8xv8b-JeM46S4e-dg@mail.gmail.com>
2015-03-09  6:40                     ` Jiri Pirko
2015-03-09 15:59                       ` Arad, Ronen
2015-03-09 16:07                         ` Jiri Pirko
2015-03-10  0:51                           ` Arad, Ronen
2015-03-10  6:39                             ` Jiri Pirko
2015-03-10  8:02                               ` Arad, Ronen
2015-03-10  8:28                                 ` Jiri Pirko
2015-03-16 22:01                                   ` John Fastabend
2015-03-17  7:00                                     ` Jiri Pirko
2015-03-17 14:31                                       ` John Fastabend
2015-03-17 20:27                                         ` roopa
2015-03-18  0:16                                           ` John Fastabend
2015-03-18  6:29                                             ` roopa
2015-03-18 15:24                                               ` John Fastabend
2015-03-18 16:55                                                 ` John Fastabend
2015-03-19  5:03                                                 ` roopa
2015-03-19  5:49                                                 ` Scott Feldman
2015-03-19 13:29                                                   ` roopa
2015-03-19 13:59                                                     ` John Fastabend
     [not found]                         ` <CAJieiUhcdfGitY7rbG11Vt_Beemz8dy3=gKtvbyVLS8O0DkgNw@mail.gmail.com>
2015-03-09 23:23                           ` Roopa Prabhu
2015-03-05  8:36 ` Jiri Pirko
2015-03-05 15:01   ` roopa
2015-03-05 15:09     ` roopa

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=54F686F2.5010404@gmail.com \
    --to=john.fastabend@gmail.com \
    --cc=davem@davemloft.net \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=roopa@cumulusnetworks.com \
    --cc=sfeldma@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 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).