From: Nick Piggin <npiggin@kernel.dk>
To: Borislav Petkov <bp@alien8.de>, Nick Piggin <npiggin@kernel.dk>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-arch@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.o
Subject: Re: Big git diff speedup by avoiding x86 "fast string" memcmp
Date: Fri, 10 Dec 2010 13:38:00 +1100 [thread overview]
Message-ID: <20101210023800.GD3331@amd> (raw)
In-Reply-To: <20101209133709.GA3133@a1.tnic>
On Thu, Dec 09, 2010 at 02:37:09PM +0100, Borislav Petkov wrote:
> On Thu, Dec 09, 2010 at 06:09:38PM +1100, Nick Piggin wrote:
> > +static inline int dentry_memcmp(const unsigned char *cs,
> > + const unsigned char *ct, size_t count)
> > +{
> > + while (count) {
> > + int ret = (*cs != *ct);
> > + if (ret)
> > + return ret;
> > + cs++;
> > + ct++;
> > + count--;
> > + }
> > + return 0;
> > +}
>
> we have a memcmp() in lib/string.c. Maybe reuse it from there?
Well I think I prefer it to be inline so it doesn't clobber registers,
and also so that it isn't required to carry an integer value to return
(only boolean) if that might help.
I might also change it a bit and take advantage of the fact we won't
have a zero sized count -- this could move the loop branch to after the
values are loaded, and would mean that the load will get underway
even if the branch is mispredicted...
WARNING: multiple messages have this Message-ID (diff)
From: Nick Piggin <npiggin@kernel.dk>
To: Borislav Petkov <bp@alien8.de>, Nick Piggin <npiggin@kernel.dk>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-arch@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: Big git diff speedup by avoiding x86 "fast string" memcmp
Date: Fri, 10 Dec 2010 13:38:00 +1100 [thread overview]
Message-ID: <20101210023800.GD3331@amd> (raw)
Message-ID: <20101210023800.6DlkVqSI6RAuz09EzEId5GmmfSdulm60nVXhnSjHRHw@z> (raw)
In-Reply-To: <20101209133709.GA3133@a1.tnic>
On Thu, Dec 09, 2010 at 02:37:09PM +0100, Borislav Petkov wrote:
> On Thu, Dec 09, 2010 at 06:09:38PM +1100, Nick Piggin wrote:
> > +static inline int dentry_memcmp(const unsigned char *cs,
> > + const unsigned char *ct, size_t count)
> > +{
> > + while (count) {
> > + int ret = (*cs != *ct);
> > + if (ret)
> > + return ret;
> > + cs++;
> > + ct++;
> > + count--;
> > + }
> > + return 0;
> > +}
>
> we have a memcmp() in lib/string.c. Maybe reuse it from there?
Well I think I prefer it to be inline so it doesn't clobber registers,
and also so that it isn't required to carry an integer value to return
(only boolean) if that might help.
I might also change it a bit and take advantage of the fact we won't
have a zero sized count -- this could move the loop branch to after the
values are loaded, and would mean that the load will get underway
even if the branch is mispredicted...
next prev parent reply other threads:[~2010-12-10 2:38 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 7:09 Big git diff speedup by avoiding x86 "fast string" memcmp Nick Piggin
2010-12-09 13:37 ` Borislav Petkov
2010-12-09 13:37 ` Borislav Petkov
2010-12-10 2:38 ` Nick Piggin [this message]
2010-12-10 2:38 ` Nick Piggin
2010-12-10 4:27 ` Nick Piggin
2010-12-10 14:23 ` J. R. Okajima
2010-12-13 1:45 ` Nick Piggin
2010-12-13 7:29 ` J. R. Okajima
2010-12-13 8:25 ` Nick Piggin
2010-12-13 8:25 ` Nick Piggin
2010-12-14 19:01 ` J. R. Okajima
2010-12-15 4:06 ` Nick Piggin
2010-12-15 5:57 ` J. R. Okajima
2010-12-15 13:15 ` Boaz Harrosh
2010-12-15 18:00 ` David Miller
2010-12-16 9:53 ` Boaz Harrosh
2010-12-16 13:13 ` Nick Piggin
2010-12-16 14:03 ` Boaz Harrosh
2010-12-16 14:15 ` Nick Piggin
2010-12-16 16:51 ` Linus Torvalds
2010-12-16 17:57 ` David Miller
2010-12-16 17:57 ` David Miller
2010-12-15 4:38 ` Américo Wang
2010-12-15 4:38 ` Américo Wang
2010-12-15 5:54 ` Nick Piggin
2010-12-15 7:12 ` Linus Torvalds
2010-12-15 23:09 ` Tony Luck
2010-12-16 2:34 ` Nick Piggin
-- strict thread matches above, loose matches on Subject: below --
2010-12-18 22:54 George Spelvin
2010-12-18 22:54 ` George Spelvin
2010-12-19 14:28 ` Boaz Harrosh
2010-12-19 14:28 ` Boaz Harrosh
2010-12-19 15:46 ` Nick Piggin
2010-12-19 17:06 ` George Spelvin
2010-12-21 9:26 ` Nick Piggin
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=20101210023800.GD3331@amd \
--to=npiggin@kernel.dk \
--cc=bp@alien8.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.o \
--cc=torvalds@linux-foundation.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).