git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Alexander Monakov <amonakov@ispras.ru>
Cc: Phillip Wood <phillip.wood@dunelm.org.uk>,  git@vger.kernel.org
Subject: Re: [PATCH 2/2] xdiff: optimize xdl_hash_record_verbatim
Date: Mon, 08 Sep 2025 14:04:16 -0700	[thread overview]
Message-ID: <xmqq8qiowt9r.fsf@gitster.g> (raw)
In-Reply-To: <abb2bc1a-e68b-85a3-2562-53328fb502c6@ispras.ru> (Alexander Monakov's message of "Mon, 8 Sep 2025 22:06:56 +0300 (MSK)")

Alexander Monakov <amonakov@ispras.ru> writes:

> On Wed, 20 Aug 2025, Junio C Hamano wrote:
>
>> The thread has gone quiet.  I assume everybody is happy with the
>> result?  Can we have a hopefully final v2 iteration of these
>> patches, to address the updated to the table (this thread), to
>> squelch the __asm__() issue [*asm*], and a reword you mentioned
>> [*reword*] against Phillip's review?
>
> I was expecting that Phillip would come back to the question of underwhelming
> performance improvement he was seeing on his CPU. I was working on an
> alternative approach to speed up that function, which I just sent in the v2
> thread: https://lore.kernel.org/git/20250908184939.16338-4-amonakov@ispras.ru/
> It does not depend on the performance of integer multiplication anymore,
> so it should work better from architecture neutrality point of view.
>
> I'm not sure what's the current status though, it seems nobody gave the original
> two patches a Reviewed-by?
>
> If the proposed changes in v2 are too sudden, what happens now?

Well, it has been quite a while since I asked, and the last round,
which looked reasonably well done, is now in 'next' and is about to
graduate to 'master'.  So, if there are further good changes on top,
can you make them incremental on top of 'master' after I push out
today's integration result?

Thanks.

  reply	other threads:[~2025-09-08 21:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28 19:05 [PATCH 0/2] optimize string hashing in xdiff Alexander Monakov
2025-07-28 19:05 ` [PATCH 1/2] xdiff: refactor xdl_hash_record() Alexander Monakov
2025-07-28 19:05 ` [PATCH 2/2] xdiff: optimize xdl_hash_record_verbatim Alexander Monakov
2025-07-28 20:50   ` Junio C Hamano
2025-07-28 20:57     ` Alexander Monakov
2025-08-04 13:49   ` Phillip Wood
2025-08-04 14:39     ` Alexander Monakov
2025-08-11 13:13       ` Phillip Wood
2025-08-11 14:14         ` Alexander Monakov
2025-08-12 17:56           ` Alexander Monakov
2025-08-20 21:34             ` Junio C Hamano
2025-09-08 19:06               ` Alexander Monakov
2025-09-08 21:04                 ` Junio C Hamano [this message]
2025-08-13 13:10           ` Phillip Wood
2025-07-28 19:32 ` [PATCH 0/2] optimize string hashing in xdiff Junio C Hamano
2025-07-28 19:56   ` Eli Schwartz
2025-07-28 20:54     ` Junio C Hamano
2025-07-28 20:25   ` Alexander Monakov
2025-08-14 15:01     ` Junio C Hamano
2025-08-28 23:40     ` Junio C Hamano
2025-08-29  1:13       ` Jacob Keller
2025-08-29  3:09       ` Elijah Newren

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=xmqq8qiowt9r.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=amonakov@ispras.ru \
    --cc=git@vger.kernel.org \
    --cc=phillip.wood@dunelm.org.uk \
    /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).