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>, <tedheadster@gmail•com>
Subject: Re: [PATCH linux-next] net: record times of netdev_budget exhausted
Date: Wed, 7 Dec 2022 16:17:32 +0800 (CST) [thread overview]
Message-ID: <202212071617323068233@zte.com.cn> (raw)
In-Reply-To: <CANn89iKqb64sLT2r+2YrpDyMfZ8T6z2Ygtby-ruVNNYvniaV0g@mail.gmail.com>
> Sure, but netdev_budget set to 1 is extreme, don't you think ???
Yes of course, that is just a test to show the difference.
> We prefer not changing /proc file format as much as we can, they are
> deprecated/legacy.
Should we add some explain of the deprecation in code or doc?
As it's deprecated, I think it's NAK for this patch.
> Presumably, modern tracing techniques can let you do what you want
> without adding new counters.
Totally agree.
next prev parent reply other threads:[~2022-12-07 8:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-03 8:12 [PATCH linux-next] net: record times of netdev_budget exhausted yang.yang29
2022-12-03 10:06 ` kernel test robot
2022-12-03 16:50 ` kernel test robot
2022-12-03 16:50 ` kernel test robot
2022-12-06 1:53 ` Jakub Kicinski
2022-12-06 2:35 ` yang.yang29
2022-12-06 2:47 ` Jakub Kicinski
2022-12-07 7:27 ` yang.yang29
2022-12-07 7:58 ` Eric Dumazet
2022-12-07 8:17 ` yang.yang29 [this message]
2022-12-07 23:28 ` Jakub Kicinski
2022-12-07 12:30 ` yang.yang29
2022-12-07 23:32 ` Jakub Kicinski
2022-12-08 1:12 ` yang.yang29
2022-12-08 1:23 ` Jakub Kicinski
2022-12-08 1:42 ` yang.yang29
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=202212071617323068233@zte.com.cn \
--to=yang.yang29@zte$(echo .)com.cn \
--cc=bigeasy@linutronix$(echo .)de \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=imagedong@tencent$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=kuniyu@amazon$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=liu3101@purdue$(echo .)edu \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=petrm@nvidia$(echo .)com \
--cc=tedheadster@gmail$(echo .)com \
--cc=wujianguo@chinatelecom$(echo .)cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox