From: David Turner <dturner@twopensource.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Torsten Bögershausen" <tboegi@web.de>,
git@vger.kernel.org, mhagger@alum.mit.edu,
"David Turner" <dturner@twitter.com>
Subject: Re: [PATCH v6 2/2] refs.c: SSE4.2 optimizations for check_refname_component
Date: Thu, 05 Jun 2014 15:27:20 -0400 [thread overview]
Message-ID: <1401996440.18134.180.camel@stross> (raw)
In-Reply-To: <xmqqsinktkjv.fsf@gitster.dls.corp.google.com>
On Wed, 2014-06-04 at 14:46 -0700, Junio C Hamano wrote:
> David Turner <dturner@twopensource.com> writes:
>
> > On Wed, 2014-06-04 at 10:04 +0200, Torsten Bögershausen wrote:
> > [snip discussion of compiler flags; I'll look into a cpuid approach]
>
> Hmmmm, I am not sure if the complexity is really worth it.
>
> In any case, [PATCH 1/2] is fairly uncontroversial, so I am inclined
> to queue it by itself early without waiting for the discussion on
> 2/2 to settle.
>
> >> The name check_refname_component_1() doesn't tell too much,
> >> (check_refname_component_sse42() or check_refname_component_nonsse42() say more)
> >
> > I'll go with "_bytewise", since that's how it works.
>
> That naming assumes that there will never be any alternative
> implementation of the bytewise checker other than the one that uses
> sse42, no?
check_refname_component_1 is the non-sse (LUT) one; I assume that there
will only be one implementation of that (and if there's later another
one we can rename it). I guess this is strong evidence for _1 being a
bad name.
prev parent reply other threads:[~2014-06-05 19:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 3:38 [PATCH v6 1/2] refs.c: optimize check_refname_component() David Turner
2014-06-04 3:38 ` [PATCH v6 2/2] refs.c: SSE4.2 optimizations for check_refname_component David Turner
2014-06-04 8:04 ` Torsten Bögershausen
2014-06-04 11:21 ` Duy Nguyen
2014-06-04 14:25 ` Torsten Bögershausen
2014-06-04 21:16 ` David Turner
2014-06-05 12:30 ` Torsten Bögershausen
2014-06-05 12:58 ` Ondřej Bílka
2014-06-05 19:26 ` David Turner
2014-06-05 21:42 ` Torsten Bögershausen
2014-06-05 22:02 ` David Turner
2014-06-04 21:14 ` David Turner
2014-06-04 21:46 ` Junio C Hamano
2014-06-05 19:27 ` David Turner [this message]
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=1401996440.18134.180.camel@stross \
--to=dturner@twopensource.com \
--cc=dturner@twitter.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mhagger@alum.mit.edu \
--cc=tboegi@web.de \
/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).