Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 6 Dec 2022 13:48:12 +0800 (CST)
Message-ID: <202212061348121276979@zte.com.cn>
In-Reply-To: <CANn89iK4Cn-+BgJEuGSWF=PTfDPWuCy8ci75664+98ajt_+3Xw@mail.gmail.com>
References: 202212050936120314474@zte.com.cn,20221205175354.3949c6bb@kernel.org,CANn89iK4Cn-+BgJEuGSWF=PTfDPWuCy8ci75664+98ajt_+3Xw@mail.gmail.com
Mime-Version: 1.0
From:   <yang.yang29@zte.com.cn>
To:     <edumazet@google.com>
Cc:     <kuba@kernel.org>, <davem@davemloft.net>, <pabeni@redhat.com>,
        <bigeasy@linutronix.de>, <imagedong@tencent.com>,
        <kuniyu@amazon.com>, <petrm@nvidia.com>, <liu3101@purdue.edu>,
        <wujianguo@chinatelecom.cn>, <netdev@vger.kernel.org>,
        <linux-kernel@vger.kernel.org>
Subject: =?UTF-8?B?UmU6IFtQQVRDSCBsaW51eC1uZXh0IHYyXSBuZXQ6IHJlY29yZCB0aW1lcyBvZiBuZXRkZXZfYnVkZ2V0IGV4aGF1c3RlZA==?=
Content-Type: text/plain;
        charset="UTF-8"
Precedence: bulk

On Tue, Dec 6, 2022 at 11:18 AM Eric Dumazet <edumazet@google.com,> wrote:
> Yes, and if we really want to track all these kinds of events the
> break caused by need_resched() in do_softirq would
> also need some monitoring.

I think this situation is a bit different. The break caused by
need_resched() in __do_softirq() is some kind of internal
events, kernel hacker may track it by something like tracepoint.

But netdev_budget* are sysctl for administrator, when
administrator adjust them, they may want to see the
effect in a direct or easy way.