From: David Miller <davem@davemloft.net>
To: vivien.didelot@savoirfairelinux.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel@savoirfairelinux.com, f.fainelli@gmail.com,
andrew@lunn.ch
Subject: Re: [PATCH net-next v2 0/5] net: dsa: use per-port upstream port
Date: Tue, 05 Dec 2017 18:02:57 -0500 (EST) [thread overview]
Message-ID: <20171205.180257.263794205941951292.davem@davemloft.net> (raw)
In-Reply-To: <20171205203413.3342-1-vivien.didelot@savoirfairelinux.com>
From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
Date: Tue, 5 Dec 2017 15:34:08 -0500
> An upstream port is a local switch port used to reach a CPU port.
>
> DSA still considers a unique CPU port in the whole switch fabric and
> thus return a unique upstream port for a given switch. This is wrong in
> a multiple CPU ports environment.
>
> We are now switching to using the dedicated CPU port assigned to each
> port in order to get rid of the deprecated unique tree CPU port.
>
> This patchset makes the dsa_upstream_port() helper take a port argument
> and goes one step closer complete support for multiple CPU ports.
>
> Changes in v2:
> - reverse-christmas-tree-fy variables
Series applied, thanks Vivien.
prev parent reply other threads:[~2017-12-05 23:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 20:34 [PATCH net-next v2 0/5] net: dsa: use per-port upstream port Vivien Didelot
2017-12-05 20:34 ` [PATCH net-next v2 1/5] net: dsa: mv88e6xxx: egress floods all DSA ports Vivien Didelot
2017-12-05 20:34 ` [PATCH net-next v2 2/5] net: dsa: mv88e6xxx: helper to setup upstream port Vivien Didelot
2017-12-05 20:34 ` [PATCH net-next v2 3/5] net: dsa: mv88e6xxx: setup global " Vivien Didelot
2017-12-05 20:34 ` [PATCH net-next v2 4/5] net: dsa: assign a CPU port to DSA port Vivien Didelot
2017-12-05 20:34 ` [PATCH net-next v2 5/5] net: dsa: return per-port upstream port Vivien Didelot
2017-12-05 23:02 ` 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=20171205.180257.263794205941951292.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=kernel@savoirfairelinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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).