From: Al Viro <viro@zeniv.linux.org.uk>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: David Laight <David.Laight@aculab.com>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] seq_file: Optimize seq_puts()
Date: Fri, 19 Apr 2024 22:32:40 +0100 [thread overview]
Message-ID: <20240419213240.GE2118490@ZenIV> (raw)
In-Reply-To: <5e5cde3e-f3ad-4a9b-bc02-1c473affdcb1@wanadoo.fr>
On Fri, Apr 19, 2024 at 10:38:15PM +0200, Christophe JAILLET wrote:
> Le 16/04/2024 à 22:56, David Laight a écrit :
> > From: Al Viro
> > > Sent: 15 April 2024 22:01
> > ...
> > > No need to make it a macro, actually. And I would suggest going
> > > a bit further:
> > >
> > > static inline void seq_puts(struct seq_file *m, const char *s)
> >
> > That probably needs to be 'always_inline'.
> >
> > > {
> > > if (!__builtin_constant_p(*s))
> > > __seq_puts(m, s);
> > > else if (s[0] && !s[1])
> > > seq_putc(m, s[0]);
> > > else
> > > seq_write(m, s, __builtin_strlen(s));
> > > }
> >
> > You missed seq_puts(m, "");
> >
> > I did wonder about checking sizeof(s) <= 2 in the #define version.
>
> git grep seq_puts.*\"[^\\].\" | wc -l
> 77
>
> What would you do in this case?
> 2 seq_putc() in order to save a memcpy(..., 2), that's it?
Not a damn thing - just have it call seq_write(). Note that
if (s[0] && !s[1])
which triggers only on single-character strings.
next prev parent reply other threads:[~2024-04-19 21:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 13:29 [PATCH] seq_file: Optimize seq_puts() Christophe JAILLET
2024-04-15 20:47 ` Christophe JAILLET
2024-04-15 21:00 ` Al Viro
2024-04-16 20:56 ` David Laight
2024-04-17 1:04 ` Al Viro
2024-04-19 18:59 ` Christophe JAILLET
2024-04-19 20:38 ` Christophe JAILLET
2024-04-19 21:32 ` Al Viro [this message]
2024-04-21 17:21 ` David Laight
2024-04-17 7:53 ` Rasmus Villemoes
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=20240419213240.GE2118490@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=David.Laight@aculab.com \
--cc=brauner@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=jack@suse.cz \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.