All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: David Turner <dturner@twopensource.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: Wed, 04 Jun 2014 14:46:28 -0700	[thread overview]
Message-ID: <xmqqsinktkjv.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <1401916476.18134.165.camel@stross> (David Turner's message of "Wed, 04 Jun 2014 17:14:36 -0400")

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?

>> can I suggest to move all SSE code out to a file under compat/,
>> like compat/refs_sse42.c, or something similar ?
>
> Since this is a relatively small section of code, I think that would be
> overkill.  Does anyone else have an opinion?

If we foresee people on other architectures to invent different
vectorized implementations on their favourite archs, we may end up
separating it out into compat/.  I have no opinion on how likely
that will happen, though, and because this is a small piece of code
right now, it shouldn't be too painful to reorganize when the time
comes.

  reply	other threads:[~2014-06-04 21:46 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 [this message]
2014-06-05 19:27         ` David Turner

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=xmqqsinktkjv.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=dturner@twitter.com \
    --cc=dturner@twopensource.com \
    --cc=git@vger.kernel.org \
    --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 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.