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: Re: [PATCH linux-next v2] net: record times of netdev_budget exhausted
Date: Tue, 6 Dec 2022 13:48:12 +0800 (CST) [thread overview]
Message-ID: <202212061348121276979@zte.com.cn> (raw)
In-Reply-To: <CANn89iK4Cn-+BgJEuGSWF=PTfDPWuCy8ci75664+98ajt_+3Xw@mail.gmail.com>
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.
prev parent reply other threads:[~2022-12-06 5:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 1:36 [PATCH linux-next v2] net: record times of netdev_budget exhausted yang.yang29
2022-12-06 1:53 ` Jakub Kicinski
2022-12-06 3:18 ` Eric Dumazet
2022-12-06 5:48 ` yang.yang29 [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=202212061348121276979@zte.com.cn \
--to=yang.yang29@zte.com.cn \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=imagedong@tencent.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liu3101@purdue.edu \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=wujianguo@chinatelecom.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.