From: Andrew Morton <akpm@linux-foundation.org>
To: Hongbo Li <lihongbo22@huawei.com>
Cc: <kees@kernel.org>, <andy@kernel.org>, <trondmy@kernel.org>,
<anna@kernel.org>, <gregkh@linuxfoundation.org>,
<linux-hardening@vger.kernel.org>, <linux-mm@kvack.org>,
<linux-nfs@vger.kernel.org>
Subject: Re: [PATCH -next v3 1/3] lib/string_choices: Add str_true_false()/str_false_true() helper
Date: Wed, 28 Aug 2024 13:25:09 -0700 [thread overview]
Message-ID: <20240828132509.4447ff09665fa0d7b8020294@linux-foundation.org> (raw)
In-Reply-To: <a6ea03c9-f92b-4faa-b924-8df58484fb13@huawei.com>
On Wed, 28 Aug 2024 11:49:51 +0800 Hongbo Li <lihongbo22@huawei.com> wrote:
> > Anything which is calling these functions is not performance-sensitive,
> > so optimizing for space is preferred. An out-of-line function which
> > returns a const char * will achieve this?
> I think this helper can achieve this. Because it is tiny enough, the
> compiler will handle this like #define macro (do the replacement)
> without allocating extra functional stack. On the contrary, if it is
> implemented as a non-inline function, it will cause extra functional
> stack when it was called every time. And it also should be implemented
> in a source file (.c file), not in header file(.h file).
No, my concern is that if, for example, str_high_low() gets used in 100
.c files then we get 100 copies of the strings "high" and "low" in
vmlinux. Making str_high_low() uninlined would fix this.
However a quick experiment tells me that the compiler and linker are
indeed able to perform this cross-object-file optimization:
--- a/fs/open.c~a
+++ a/fs/open.c
@@ -34,6 +34,8 @@
#include <linux/mnt_idmapping.h>
#include <linux/filelock.h>
+#include <linux/string_choices.h>
+
#include "internal.h"
int do_truncate(struct mnt_idmap *idmap, struct dentry *dentry,
@@ -42,6 +44,8 @@ int do_truncate(struct mnt_idmap *idmap,
int ret;
struct iattr newattrs;
+ printk("%s\n", frozzle(dentry == NULL));
+
/* Not pretty: "inode->i_size" shouldn't really be signed. But it is. */
if (length < 0)
return -EINVAL;
--- a/fs/inode.c~a
+++ a/fs/inode.c
@@ -22,6 +22,9 @@
#include <linux/iversion.h>
#include <linux/rw_hint.h>
#include <trace/events/writeback.h>
+
+#include <linux/string_helpers.h>
+
#include "internal.h"
/*
@@ -110,6 +113,8 @@ static struct inodes_stat_t inodes_stat;
static int proc_nr_inodes(const struct ctl_table *table, int write, void *buffer,
size_t *lenp, loff_t *ppos)
{
+ printk("%s\n", frozzle(table == NULL));
+
inodes_stat.nr_inodes = get_nr_inodes();
inodes_stat.nr_unused = get_nr_inodes_unused();
return proc_doulongvec_minmax(table, write, buffer, lenp, ppos);
--- a/include/linux/string_choices.h~a
+++ a/include/linux/string_choices.h
@@ -4,6 +4,11 @@
#include <linux/types.h>
+static inline const char *frozzle(bool v)
+{
+ return v ? "frizzle" : "frazzle";
+}
+
static inline const char *str_enable_disable(bool v)
{
return v ? "enable" : "disable";
_
x1:/usr/src/25> strings vmlinux|grep frazzle
frazzle
x1:/usr/src/25>
See, only one copy!
next prev parent reply other threads:[~2024-08-28 20:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 2:45 [PATCH -next v3 0/3] " Hongbo Li
2024-08-27 2:45 ` [PATCH -next v3 1/3] lib/string_choices: " Hongbo Li
2024-08-27 23:42 ` Andrew Morton
2024-08-28 1:48 ` Hongbo Li
2024-08-28 3:22 ` Andrew Morton
2024-08-28 3:49 ` Hongbo Li
2024-08-28 20:25 ` Andrew Morton [this message]
2024-08-29 1:12 ` Hongbo Li
2024-09-05 16:51 ` (subset) " Kees Cook
2024-08-28 12:59 ` Andy Shevchenko
2024-08-27 2:45 ` [PATCH -next v3 2/3] mm: make use of str_true_false helper Hongbo Li
2024-08-27 2:45 ` [PATCH -next v3 3/3] nfs make use of str_false_true helper Hongbo Li
2024-08-27 3:33 ` Matthew Wilcox
2024-08-27 6:15 ` Hongbo Li
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=20240828132509.4447ff09665fa0d7b8020294@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andy@kernel.org \
--cc=anna@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kees@kernel.org \
--cc=lihongbo22@huawei.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@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