From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 17076 invoked from network); 2 May 2021 10:54:41 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 2 May 2021 10:54:41 -0000 Received: from duke.felloff.net ([216.126.196.34]) by 1ess; Sun May 2 06:51:46 -0400 2021 Message-ID: <4AD2CDAB319DDBA8AC51728729CBF224@felloff.net> Date: Sun, 02 May 2021 12:51:34 +0200 From: cinap_lenrek@felloff.net To: 9front@9front.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: XML over XMPP general-purpose interface Subject: Re: [9front] Re: memory(2): mention tsmemcmp Reply-To: 9front@9front.org Precedence: bulk I think it should be explained how it works. Basically, tsmemcmp always reads all the bytes and does NOT stop early when it sees a difference. That makes its runtime only a function of N, not the contents of the data so here can be no information gathered about the data from measuring its runtime behaviour or cache side-effects. -- cinap