Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Message-ID: <9bd95c0ad91bd490adf2b6e57495411a0f72fe50.camel@gmx.de>
Subject: Re: data loss when doing ls-remote and piped to command
From:   Mike Galbraith <efault@gmx.de>
To:     Rolf Eike Beer <eb@emlix.com>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        Junio C Hamano <gitster@pobox.com>
Cc:     Git List Mailing <git@vger.kernel.org>,
        Tobias Ulmer <tu@emlix.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Date:   Sat, 18 Sep 2021 08:33:38 +0200
In-Reply-To: <2722184.bRktqFsmb4@devpool47>
References: <6786526.72e2EbofS7@devpool47>
         <CAHk-=wgyk0mwYcMRC8HakzoAKL2Y3gwzD433tqKYYhV+r1PLnA@mail.gmail.com>
         <xmqq7dfgtfpt.fsf@gitster.g> <2722184.bRktqFsmb4@devpool47>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.41.2 
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Fri, 2021-09-17 at 08:59 +0200, Rolf Eike Beer wrote:
>
> What you need is a _fast_ git server. kernel.org or github.com seem to b=
e too
> slow for this if you don't sit somewhere in their datacenter. Use someth=
ing in
> your local network, a Xeon E5 with lot's of RAM and connected with 1GBit=
/s
> Ethernet in my case.

Even faster: what's coming across that wire should be a constant (is?),
variable is only delivery/consumption jitter.  If there's really really
a pipe problem lurking, you should also be able to trigger by saving
the data once, and just catting it, letting interrupts etc provide
jitter.  Which stdout is left of '|' in a script shouldn't matter one
whit to the interpreter/kernel conversation, they're all the same.

That said, if I had a reproducer I was confident pointed to the kernel,
I'd try to bisect.. boring as hell, but highly effective.

	-Mike