From: <yang.yang29@zte.com.cn>
To: <kuba@kernel.org>
Cc: <edumazet@google.com>, <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: Thu, 8 Dec 2022 09:12:06 +0800 (CST) [thread overview]
Message-ID: <202212080912066313234@zte.com.cn> (raw)
In-Reply-To: <20221207153256.6c0ec51a@kernel.org>
> In my experience - no this is not useful.
Received, thanks!
> Sorry if this is too direct, but it seems to me like you're trying hard
> to find something useful to do in this area without a clear use case.
I see maybe this is a too special scenes, not suitable. The motivation
is we see lots of time_squeeze on our working machines, and want to
tuning, but our kernel are not ready to use threaded NAPI. And we
did see performance difference on different netdev_budget* in
preliminary tests.
> We have coding tasks which would definitely be useful and which nobody
> has time to accomplish. Please ask if you're trying to find something
> to do.
We focus on 5G telecom machine, which has huge TIPC packets in the
intranet. If it's related, we are glad to do it with much appreciate of your
indicate!
Thanks.
next prev parent reply other threads:[~2022-12-08 1:13 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
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 [this message]
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=202212080912066313234@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=tedheadster@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox