From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org, linux-mm@kvack.org
Subject: tcp_bind_bucket is missing from slabinfo
Date: Fri, 23 Feb 2018 22:50:30 -0800 [thread overview]
Message-ID: <20180223225030.2e8ef122@shemminger-XPS-13-9360> (raw)
Somewhere back around 3.17 the kmem cache "tcp_bind_bucket" dropped out
of /proc/slabinfo. It turns out the ss command was dumpster diving
in slabinfo to determine the number of bound sockets and now it always
reports 0.
Not sure why, the cache is still created but it doesn't
show in slabinfo. Could it be some part of making slab/slub common code
(or network namespaces). The cache is created in tcp_init but not visible.
Any ideas?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2018-02-24 6:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-24 6:50 Stephen Hemminger [this message]
2018-02-24 14:35 ` Matthew Wilcox
2018-02-24 18:58 ` Stephen Hemminger
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=20180223225030.2e8ef122@shemminger-XPS-13-9360 \
--to=stephen@networkplumber.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.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