> -----Original Message-----
> From: Jakub Kicinski <[email protected]>
> Sent: Tuesday, July 9, 2019 3:17 AM
> To: Sudarsana Reddy Kalluru <[email protected]>
> Cc: [email protected]; [email protected]; Michal Kalderon
> <[email protected]>; Ariel Elior <[email protected]>; Jiri Pirko
> <[email protected]>
> Subject: Re: [EXT] Re: [PATCH net-next v2 4/4] qed*: Add devlink support for
> configuration attributes.
>
> On Mon, 8 Jul 2019 02:31:15 +0000, Sudarsana Reddy Kalluru wrote:
> > > > > > + Type: u8
> > > > > > + Configuration mode: Permanent
> > > > > > +
> > > > > > +dcbx_mode [PORT, DRIVER-SPECIFIC]
> > > > > > + Configure DCBX mode for the device.
> > > > > > + Supported dcbx modes are,
> > > > > > + Disabled(0), IEEE(1), CEE(2) and
> > > > > > Dynamic(3)
> > > > > > + Type: u8
> > > > > > + Configuration mode: Permanent
> > > > >
> > > > > Why is this a permanent parameter?
> > > > >
> > > > This specifies the dcbx_mode to be configured in non-volatile memory.
> > > > The value is persistent and is used in the next load of OS or the mfw.
> > >
> > > And it can't be changed at runtime?
> >
> > Run time dcbx params are not affected via this interface, it only
> > updates config on permanent storage of the port.
>
> IOW it affects the defaults after boot? It'd be preferable to have the DCB
> uAPI handle "persistent"/default settings if that's the case.
Yes, it's effective after the reboot. Thanks for your suggestion.
