From: Imran Khan <imran.f.khan@oracle.com>
To: cl@linux.com, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [RFC PATCH 0/2] mm, slub: Use stackdepot to store user information for slub object
Date: Tue, 31 Aug 2021 16:25:37 +1000 [thread overview]
Message-ID: <20210831062539.898293-1-imran.f.khan@oracle.com> (raw)
This series of patches proposes use of STACKDEPOT to
store user (SLAB_STORE_USER) information of a slub object.
As stack traces corresponding to each unique allocation
and freeing context can be saved and retrieved from STACKDEPOT,
we can reduce size of each object (~256 bytes) and hence save
memory without losing any information.
*PATCH-1: Makes STACKDEPOT explicitly configurable, so that
it can be enabled for storing allocation/freeing stack traces.
*PATCH-2: Uses STACKDEPOT to store allocation/freeing context
for a slub object.
I have marked this series as RFC, so that I can get feedback
about this change, because this change just involves debugging
framework and does not add any value to production scenarios.
Imran Khan (2):
lib, stackdepot: Add input prompt for STACKDEPOT option.
mm, slub: Use stackdepot to store user information for slub object.
lib/Kconfig | 3 +-
mm/slub.c | 87 +++++++++++++++++++++++++++++------------------------
2 files changed, 50 insertions(+), 40 deletions(-)
--
2.25.1
next reply other threads:[~2021-08-31 6:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 6:25 Imran Khan [this message]
2021-08-31 6:25 ` [RFC PATCH 1/2] lib, stackdepot: Add input prompt for STACKDEPOT option Imran Khan
2021-08-31 11:25 ` Vlastimil Babka
2021-09-01 6:28 ` imran.f.khan
2021-08-31 15:54 ` Geert Uytterhoeven
2021-08-31 6:25 ` [RFC PATCH 2/2] mm, slub: Use stackdepot to store user information for slub object Imran Khan
2021-08-31 12:06 ` Vlastimil Babka
2021-09-01 6:36 ` imran.f.khan
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=20210831062539.898293-1-imran.f.khan@oracle.com \
--to=imran.f.khan@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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