mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Andy Shevchenko' <andriy.shevchenko@linux.intel.com>,
	Kees Cook <keescook@chromium.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Andy Shevchenko <andy@kernel.org>,
	Rasmus Villemoes <linux@rasmusvillemoes.dk>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: RE: [PATCH v1 1/1] lib/string: Use strchr() in strpbrk()
Date: Sat, 28 Jan 2023 14:51:47 +0000	[thread overview]
Message-ID: <a903947619f94dfa88d3dd147b7a5e95@AcuMS.aculab.com> (raw)
In-Reply-To: <20230127155135.27153-1-andriy.shevchenko@linux.intel.com>

From: Andy Shevchenko
> Sent: 27 January 2023 15:52
> 
> Use strchr() instead of open coding it as it's done elsewhere in
> the same file. Either we will have similar to what it was or possibly
> better performance in case architecture implements its own strchr().

Except that you get a whole load of calls to strchr() for (typically)
very few characters.
So the cost of the calls dominates, anything that tries to speed up
strchr() for long strings will also slow things down.

Plausibly this version (untested) is faster!

char *strbprk(const char *str, const char *seps)
{
	const char *found, *try;

	do {
		if (*!seps)
			return NULL;
		found = strchr(str, *seps++);
	} while (!found);

	while (*seps) {
		try = memchr(str, *seps++, found - str);
		if (try)
			found = try;
	}

	return (char *)found;
}

Although I very much doubt strpbrk() is used anywhere where
performance matters.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)


  parent reply	other threads:[~2023-01-28 14:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-27 15:51 Andy Shevchenko
2023-01-27 18:55 ` Kees Cook
2023-01-28 14:51 ` David Laight [this message]
2023-01-28 19:54   ` Andy Shevchenko
2023-01-28 22:35     ` David Laight

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=a903947619f94dfa88d3dd147b7a5e95@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=akpm@linux-foundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=andy@kernel.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@rasmusvillemoes.dk \
    /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

all inboxes | Powered by JetHome®