[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230114090311.1adf0176@hermes.local>
Date: Sat, 14 Jan 2023 09:03:11 -0800
From: Stephen Hemminger <stephen@...workplumber.org>
To: Jamal Hadi Salim <jhs@...atatu.com>
Cc: Hangbin Liu <liuhangbin@...il.com>, netdev@...r.kernel.org,
Cong Wang <xiyou.wangcong@...il.com>,
Jiri Pirko <jiri@...nulli.us>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
David Ahern <dsahern@...nel.org>
Subject: Re: [PATCH iproute2-next 2/2] tc: add new attr TCA_EXT_WARN_MSG
On Sat, 14 Jan 2023 07:59:39 -0500
Jamal Hadi Salim <jhs@...atatu.com> wrote:
> This is not really an error IMO (and therefore doesnt belong in
> stderr). If i send a request to add an
> entry and ask that it is installed both in the kernel as well as
> offloaded into h/w and half of that
> worked (example hardware rejected it for some reason) then the event
> generated (as observed by
> f.e. tc mon) will appear in TCA_EXT_WARN_MSG and the consumer of that
> event needs to see it
> if they are using the json format.
>
Ok, but use lower case for JSON tag following existing conventions.
Note: json support in monitor mode is incomplete for many of the
commands bridge, ip, tc, devlink. It doesn't always generate valid JSON
yet.
Powered by blists - more mailing lists