lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Sun, 5 Jan 2020 00:27:42 +0200
From:   Vladimir Oltean <olteanv@...il.com>
To:     Andrew Lunn <andrew@...n.ch>
Cc:     David Miller <davem@...emloft.net>,
        netdev <netdev@...r.kernel.org>,
        Vivien Didelot <vivien.didelot@...il.com>,
        Chris Healy <Chris.Healy@....aero>
Subject: Re: [PATCH net] net: dsa: mv88e6xxx: Preserve priority went setting
 CPU port.

On Sun, 5 Jan 2020 at 00:05, Andrew Lunn <andrew@...n.ch> wrote:
>
> On Sat, Jan 04, 2020 at 08:56:12PM +0200, Vladimir Oltean wrote:
> > Hi Andrew,
> >
> > Is there a typo in the commit message? (went -> when)
>
> Yep. Thanks for pointing it out.
>
> >
> > On Sat, 4 Jan 2020 at 18:16, Andrew Lunn <andrew@...n.ch> wrote:
> > >
> > > The 6390 family uses an extended register to set the port connected to
> > > the CPU. The lower 5 bits indicate the port, the upper three bits are
> > > the priority of the frames as they pass through the switch, what
> > > egress queue they should use, etc. Since frames being set to the CPU
> > > are typically management frames, BPDU, IGMP, ARP, etc set the priority
> > > to 7, the reset default, and the highest.
> > >
> > > Fixes: 33641994a676 ("net: dsa: mv88e6xxx: Monitor and Management tables")
> > > Signed-off-by: Andrew Lunn <andrew@...n.ch>
> > > ---
> >
> > Offtopic: Does the switch look at VLAN PCP for these frames at all, or
> > is the priority fixed to the value from this register?
>
> I _think_ it is fixed. But this is just for "management"
> frames. Normal data frames heading to the CPU because of MAC address
> learning should have all the normal QoS operations the switch supports
> to determining their priority.
>
> > >  drivers/net/dsa/mv88e6xxx/global1.c | 5 +++++
> > >  drivers/net/dsa/mv88e6xxx/global1.h | 1 +
> > >  2 files changed, 6 insertions(+)
> > >
> > > diff --git a/drivers/net/dsa/mv88e6xxx/global1.c b/drivers/net/dsa/mv88e6xxx/global1.c
> > > index 120a65d3e3ef..ce03f155e9fb 100644
> > > --- a/drivers/net/dsa/mv88e6xxx/global1.c
> > > +++ b/drivers/net/dsa/mv88e6xxx/global1.c
> > > @@ -360,6 +360,11 @@ int mv88e6390_g1_set_cpu_port(struct mv88e6xxx_chip *chip, int port)
> > >  {
> > >         u16 ptr = MV88E6390_G1_MONITOR_MGMT_CTL_PTR_CPU_DEST;
> > >
> > > +       /* Use the default high priority for manegement frames sent to
> >
> > management
>
> Humm. What happened to my spell checker?
>
> > > +        * the CPU.
> > > +        */
> > > +       port |= MV88E6390_G1_MONITOR_MGMT_CTL_PTR_CPU_DEST_MGMTPRI;
> > > +
> > >         return mv88e6390_g1_monitor_write(chip, ptr, port);
> > >  }
> > >
> > > diff --git a/drivers/net/dsa/mv88e6xxx/global1.h b/drivers/net/dsa/mv88e6xxx/global1.h
> > > index bc5a6b2bb1e4..5324c6f4ae90 100644
> > > --- a/drivers/net/dsa/mv88e6xxx/global1.h
> > > +++ b/drivers/net/dsa/mv88e6xxx/global1.h
> > > @@ -211,6 +211,7 @@
> > >  #define MV88E6390_G1_MONITOR_MGMT_CTL_PTR_INGRESS_DEST         0x2000
> > >  #define MV88E6390_G1_MONITOR_MGMT_CTL_PTR_EGRESS_DEST          0x2100
> > >  #define MV88E6390_G1_MONITOR_MGMT_CTL_PTR_CPU_DEST             0x3000
> > > +#define MV88E6390_G1_MONITOR_MGMT_CTL_PTR_CPU_DEST_MGMTPRI     0x00e0
> >
> > I suppose this could be more nicely expressed as
> > MV88E6390_G1_MONITOR_MGMT_CTL_PTR_CPU_DEST_MGMTPRI(x)    ((x) << 5 &
> > GENMASK(7, 5)), in case somebody wants to change it from 7?
>
> It could be. But i'm not aware of any suitable existing API to
> configure this. So i went KISS and used the hard coded value.
>

No, I mean it's absolutely reasonable for the default value of the
traffic class for management traffic to be 7 rather than 0, if it's
fixed (and it's not surprising that this is the out-of-reset default).
I was just making an argument for that "7" to be more explicit for
code lurkers who don't have access to Marvell documentation...
According to your answer above, the sja1105 hardware is very similar
in behavior (its knob is called HOSTPRIO and that driver hardcodes it
to 7 too, which makes sense). It's just that the similarity is far
from obvious if you define
MV88E6390_G1_MONITOR_MGMT_CTL_PTR_CPU_DEST_MGMTPRI as 0x00e0 (my 2
cents). Had I known that Peridot does behave so similar in this
regard, I would have thought twice about attempting to create a
driver-specific devlink param for this setting [0]:

https://www.spinics.net/lists/netdev/msg614039.html

>           Andrew

Regards,
-Vladimir

Powered by blists - more mailing lists