netdev - Re: [PATCH ] net: frag: print frag_mem_limit value in sockstat proc file

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20170829.160401.1682245884573191819.davem@davemloft.net>
Date:   Tue, 29 Aug 2017 16:04:01 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     liujian56@...wei.com
Cc:     kuznet@....inr.ac.ru, yoshfuji@...ux-ipv6.org, brouer@...hat.com,
        fw@...len.de, netdev@...r.kernel.org
Subject: Re: [PATCH ] net: frag: print frag_mem_limit value in sockstat
 proc file

From: <liujian56@...wei.com>
Date: Tue, 29 Aug 2017 21:05:34 +0800

> From: liujian <liujian56@...wei.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@...wei.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.