From: Jakub Kicinski <kuba@kernel.org>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
ast@kernel.org, daniel@iogearbox.net, hawk@kernel.org,
john.fastabend@gmail.com, stephen@networkplumber.org,
simon.horman@corigine.com, sinquersw@gmail.com,
bpf@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Jason Xing <kernelxing@tencent.com>
Subject: Re: [PATCH v3 net-next 2/2] net: introduce budget_squeeze to help us tune rx behavior
Date: Tue, 14 Mar 2023 22:09:24 -0700 [thread overview]
Message-ID: <20230314220924.52dfb803@kernel.org> (raw)
In-Reply-To: <20230314131427.85135-3-kerneljasonxing@gmail.com>
On Tue, 14 Mar 2023 21:14:27 +0800 Jason Xing wrote:
> When we encounter some performance issue and then get lost on how
> to tune the budget limit and time limit in net_rx_action() function,
> we can separately counting both of them to avoid the confusion.
More details please, we can't tell whether your solution makes sense
if we don't know what your problem is.
next prev parent reply other threads:[~2023-03-15 5:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 13:14 [PATCH v3 net-next 0/2] add some detailed data when reading softnet_stat Jason Xing
2023-03-14 13:14 ` [PATCH v3 net-next 1/2] net-sysfs: display two backlog queue len separately Jason Xing
2023-03-14 15:15 ` Eric Dumazet
2023-03-14 15:37 ` Jason Xing
2023-03-14 13:14 ` [PATCH v3 net-next 2/2] net: introduce budget_squeeze to help us tune rx behavior Jason Xing
2023-03-15 5:09 ` Jakub Kicinski [this message]
2023-03-15 8:28 ` Jason Xing
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=20230314220924.52dfb803@kernel.org \
--to=kuba@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kerneljasonxing@gmail.com \
--cc=kernelxing@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.com \
--cc=sinquersw@gmail.com \
--cc=stephen@networkplumber.org \
/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;
as well as URLs for NNTP newsgroup(s).