netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <jakub.kicinski@netronome.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Jiri Pirko <jiri@resnulli.us>,
	netdev@vger.kernel.org, davem@davemloft.net, mlxsw@mellanox.com,
	idosch@mellanox.com, andrew@lunn.ch, vivien.didelot@gmail.com,
	michael.chan@broadcom.com
Subject: Re: [patch net-next 00/12] net: expose switch ID via devlink
Date: Fri, 29 Mar 2019 14:57:28 -0700	[thread overview]
Message-ID: <20190329145728.72e5a07b@cakuba.netronome.com> (raw)
In-Reply-To: <0d1e99ef-38d4-93bd-ad79-dd9002b3f468@gmail.com>

On Fri, 29 Mar 2019 14:29:11 -0700, Florian Fainelli wrote:
> > Out of curiosity, what are the shared features?  It seems mlx5 drives 
> > a lot of our API design, it'd be good if the community had a better
> > understanding of it.
> > 
> > The situation with pipelined devices is somewhat murky.  Didn't Or add
> > some from of PCIe-side looped queue to forward between PFs?
> > 
> > Presumably DSA would lean the opposite way with multiple ASICs
> > reporting the same ID?  
> 
> If you have multiple switches inter connected between each other to use
> the "D" in DSA and form a fabric of switches, then you would expect each
> port to be physically tied to a particular switch device/instance,
> because, but how they will report the switch physical ID can be of the form:
> 
> <fabric>.<switch>
> 
> where fabric is dst->index and switch is ds->index (the switch within
> the fabric).

Oh, I assumed you'd want the to all have the same switchid, and then
the "D" in DSA logic makes sure the flooding etc. works across the
ASICs..

  reply	other threads:[~2019-03-29 21:57 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-28 21:12 [patch net-next 00/12] net: expose switch ID via devlink Jiri Pirko
2019-03-28 21:12 ` [patch net-next 01/12] net: devlink: convert devlink_port_attrs bools to bits Jiri Pirko
2019-03-28 21:12 ` [patch net-next 02/12] net: devlink: extend port attrs for switch ID Jiri Pirko
2019-03-28 21:12 ` [patch net-next 03/12] net: devlink: introduce devlink_compat_switch_id_get() helper Jiri Pirko
2019-03-28 21:12 ` [patch net-next 04/12] mlxsw: Pass switch ID through devlink_port_attrs_set() Jiri Pirko
2019-03-28 21:12 ` [patch net-next 05/12] mlxsw: Remove ndo_get_port_parent_id implementation Jiri Pirko
2019-03-28 21:12 ` [patch net-next 06/12] bnxt: pass switch ID through devlink_port_attrs_set() Jiri Pirko
2019-03-28 21:12 ` [patch net-next 07/12] bnxt: remove ndo_get_port_parent_id implementation for physical ports Jiri Pirko
2019-03-28 21:12 ` [patch net-next 08/12] nfp: pass switch ID through devlink_port_attrs_set() Jiri Pirko
2019-03-28 21:12 ` [patch net-next 09/12] nfp: remove ndo_get_port_parent_id implementation Jiri Pirko
2019-03-28 21:12 ` [patch net-next 10/12] mlxsw: switch_ib: Pass valid HW id down to mlxsw_core_port_init() Jiri Pirko
2019-03-28 21:12 ` [patch net-next 11/12] dsa: pass switch ID through devlink_port_attrs_set() Jiri Pirko
2019-03-29 21:59   ` Florian Fainelli
2019-04-01 13:04     ` Jiri Pirko
2019-03-28 21:12 ` [patch net-next 12/12] net: devlink: add warning for ndo_get_port_parent_id set when not needed Jiri Pirko
2019-03-28 21:40 ` [patch net-next 00/12] net: expose switch ID via devlink Jakub Kicinski
2019-03-29  6:49   ` Jiri Pirko
2019-03-29 18:59     ` Jakub Kicinski
2019-03-29 21:21       ` Jiri Pirko
2019-03-29 22:34         ` Jakub Kicinski
2019-03-30  7:35           ` Jiri Pirko
2019-03-30 19:49             ` Jakub Kicinski
2019-03-31  8:50               ` Jiri Pirko
2019-03-31 20:57                 ` Jakub Kicinski
2019-03-29 21:29       ` Florian Fainelli
2019-03-29 21:57         ` Jakub Kicinski [this message]
2019-03-29 22:04           ` Florian Fainelli

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=20190329145728.72e5a07b@cakuba.netronome.com \
    --to=jakub.kicinski@netronome.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=idosch@mellanox.com \
    --cc=jiri@resnulli.us \
    --cc=michael.chan@broadcom.com \
    --cc=mlxsw@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=vivien.didelot@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).