From: David Miller <davem@davemloft.net>
To: liujian56@huawei.com
Cc: kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org, brouer@redhat.com,
fw@strlen.de, netdev@vger.kernel.org
Subject: Re: [PATCH ] net: frag: print frag_mem_limit value in sockstat proc file
Date: Tue, 29 Aug 2017 16:04:01 -0700 (PDT) [thread overview]
Message-ID: <20170829.160401.1682245884573191819.davem@davemloft.net> (raw)
In-Reply-To: <1504011934-17308-1-git-send-email-liujian56@huawei.com>
From: <liujian56@huawei.com>
Date: Tue, 29 Aug 2017 21:05:34 +0800
> From: liujian <liujian56@huawei.com>
>
> From 6d7b857d5( net: use lib/percpu_counter API for fragmentation mem
> accounting),
> frag_mem_limit and sum_frag_mem_limit have different value if there are
> multiple NIC RX CPU.
> Print frag_mem_limit value, then we can get more debug info.
>
> Signed-off-by: liujian <liujian56@huawei.com>
Sorry, I don't think it is justified to change the deprecated procfs
output just for this.
Use tracepoints and other similar facilities to debug situations
like this if you like.
prev parent reply other threads:[~2017-08-29 23:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 13:05 [PATCH ] net: frag: print frag_mem_limit value in sockstat proc file liujian56
2017-08-29 23:04 ` David Miller [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=20170829.160401.1682245884573191819.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=brouer@redhat.com \
--cc=fw@strlen.de \
--cc=kuznet@ms2.inr.ac.ru \
--cc=liujian56@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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