From: Greg KH <gregkh@linuxfoundation.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v3 00/11] Symbol Namespaces
Date: Wed, 21 Aug 2019 06:37:37 -0700 [thread overview]
Message-ID: <20190821133737.GB4890@kroah.com> (raw)
In-Reply-To: <nycvar.YSQ.7.76.1908210840490.19480@knanqh.ubzr>
On Wed, Aug 21, 2019 at 08:46:47AM -0400, Nicolas Pitre wrote:
> On Wed, 21 Aug 2019, Matthias Maennich wrote:
>
> > As of Linux 5.3-rc5, there are 31205 [1] exported symbols in the kernel.
> > That is a growth of roughly 1000 symbols since 4.17 (30206 [2]). There
> > seems to be some consensus amongst kernel devs that the export surface
> > is too large, and hard to reason about.
>
> This is good work.
>
> One solution for drastically reducing the effective export surface is to
> have CONFIG_TRIM_UNUSED_KSYMS=y. This is more extreme than symbol
> namespace, but might be worth mentioning nevertheless.
Oh that's amazing, I never noticed that feature. That is a nice thing,
thanks for pointing it out.
greg k-h
next prev parent reply other threads:[~2019-08-21 13:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190813121733.52480-1-maennich@google.com>
2019-08-21 11:49 ` [PATCH v3 00/11] Symbol Namespaces Matthias Maennich
2019-08-21 11:49 ` [PATCH v3 11/11] RFC: watchdog: export core symbols in WATCHDOG_CORE namespace Matthias Maennich
2019-08-21 12:39 ` Greg KH
2019-08-21 14:59 ` Guenter Roeck
2019-08-21 16:28 ` Matthias Maennich
2019-08-21 12:46 ` [PATCH v3 00/11] Symbol Namespaces Nicolas Pitre
2019-08-21 13:37 ` Greg KH [this message]
2019-08-21 20:48 ` Nicolas Pitre
2019-08-21 13:11 ` Peter Zijlstra
2019-08-21 13:38 ` Greg KH
2019-08-21 14:03 ` Matthias Maennich
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=20190821133737.GB4890@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-aspeed@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).