All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: "lode leroy" <lode_leroy@hotmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] memchr (trivial) optimization
Date: 22 Aug 2007 12:56:57 +0200	[thread overview]
Message-ID: <p73bqczzvk6.fsf@bingen.suse.de> (raw)
In-Reply-To: <BAY105-F323FF3DC8E6C544A2BBE98FFD50@phx.gbl>

"lode leroy" <lode_leroy@hotmail.com> writes:

> While profiling something completely unrelated, I noticed
> that on the workloads I used memchr for, I saw a 30%-40% improvement
> in performance, with the following trivial changes...
> (basically, it saves 3 operations for each call)

What kind of workload? I didn't think anything in tree
was memchr intensive.

-Andi

  reply	other threads:[~2007-08-22 10:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-22  9:34 [PATCH] memchr (trivial) optimization lode leroy
2007-08-22 10:56 ` Andi Kleen [this message]
2007-08-23  0:13 ` Ingo Oeser
2007-08-24  0:13   ` Matt Mackall
2007-08-24  1:03     ` Jeremy Fitzhardinge
2007-08-24  2:19       ` Matt Mackall
2007-08-24 12:54     ` Jan Engelhardt
2007-08-24 15:57       ` Matt Mackall

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=p73bqczzvk6.fsf@bingen.suse.de \
    --to=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lode_leroy@hotmail.com \
    /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.