From: Eric Dumazet <edumazet@google.com>
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Jason Xing <kernelxing@tencent.com>
Subject: Re: [PATCH net-next] net-sysfs: display two backlog queue len separately
Date: Mon, 13 Mar 2023 10:33:52 -0700 [thread overview]
Message-ID: <CANn89iLWTie6bZZR3fkuOPfVWgjmiV9er_6MPbbcM2AE13ZQLQ@mail.gmail.com> (raw)
In-Reply-To: <CAL+tcoCsQ18ae+hUwqFigerJQfhrusuOOC63Wc+ZGyGWEvSFBQ@mail.gmail.com>
On Mon, Mar 13, 2023 at 10:16 AM Jason Xing <kerneljasonxing@gmail.com> wrote:
>
> Thanks for the guidance. Scaling is a good way to go really. But I
> just would like to separate these two kinds of limits to watch them
> closely. More often we cannot decide to adjust accurately which one
> should be adjusted. Time squeeze may not be clear and we cannot
> randomly write a larger number into both proc files which may do harm
> to some external customers unless we can show some proof to them.
>
> Maybe I got something wrong. If adding some tracepoints for those
> limits in softnet_data is not elegant, please enlighten me :)
>
I dunno, but it really looks like you are re-discovering things that
we dealt with about 10 years ago.
I wonder why new ways of tracing stuff are needed nowadays, while ~10
years ago nothing
officially put and maintained forever in the kernel was needed.
next prev parent reply other threads:[~2023-03-13 17:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-11 15:17 [PATCH net-next] net-sysfs: display two backlog queue len separately Jason Xing
2023-03-12 19:02 ` Simon Horman
2023-03-13 1:55 ` Jason Xing
2023-03-13 2:28 ` Stephen Hemminger
2023-03-13 2:42 ` Jason Xing
2023-03-13 9:03 ` Jason Xing
2023-03-13 12:11 ` Simon Horman
2023-03-13 12:19 ` Jason Xing
2023-03-13 12:34 ` Eric Dumazet
2023-03-13 13:15 ` Jason Xing
2023-03-13 15:59 ` Eric Dumazet
2023-03-13 17:15 ` Jason Xing
2023-03-13 17:33 ` Eric Dumazet [this message]
2023-03-14 1:54 ` 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=CANn89iLWTie6bZZR3fkuOPfVWgjmiV9er_6MPbbcM2AE13ZQLQ@mail.gmail.com \
--to=edumazet@google.com \
--cc=davem@davemloft.net \
--cc=kerneljasonxing@gmail.com \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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).