From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [216.205.24.124]) by sourceware.org (Postfix) with ESMTP id 089B73850432 for ; Wed, 28 Oct 2020 14:29:34 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 089B73850432 Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-391-2LHzgumOOkS6CDNFH1o8-w-1; Wed, 28 Oct 2020 10:29:31 -0400 X-MC-Unique: 2LHzgumOOkS6CDNFH1o8-w-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 5C86C195CC40; Wed, 28 Oct 2020 14:29:29 +0000 (UTC) Received: from oldenburg2.str.redhat.com (ovpn-113-60.ams2.redhat.com [10.36.113.60]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 8F3C05B4B2; Wed, 28 Oct 2020 14:29:24 +0000 (UTC) From: Florian Weimer To: "H.J. Lu" Cc: Sajan Karumanchi , GNU C Library , "Carlos O'Donell" , "Mallappa, Premachandra" Subject: Re: [PATCH 1/1] x86: Optimizing memcpy for AMD Zen architecture. References: <20201022045005.17371-1-sajan.karumanchi@amd.com> <20201022045005.17371-2-sajan.karumanchi@amd.com> Date: Wed, 28 Oct 2020 15:29:22 +0100 In-Reply-To: (H. J. Lu's message of "Wed, 28 Oct 2020 07:00:08 -0700") Message-ID: <87zh46v2yl.fsf@oldenburg2.str.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.11 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-6.3 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Oct 2020 14:29:55 -0000 * H. J. Lu: >> if (cpu_features->data_cache_size !=3D 0) >> - data =3D cpu_features->data_cache_size; >> + { >> + if (data =3D=3D 0 || cpu_features->basic.kind !=3D arch_kind_amd) >> + data =3D cpu_features->data_cache_size; >> + } > > This looks wrong. cpu_features->data_cache_size is set by > GLIBC tunables: > > -- Tunable: glibc.cpu.x86_data_cache_size > The =E2=80=98glibc.cpu.x86_data_cache_size=E2=80=99 tunable allows t= he user to set > data cache size in bytes for use in memory and string routines. > > This tunable is specific to i386 and x86-64. > > Why is it ignored? So we should revert those two hunks only? Thanks, Florian --=20 Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'N= eill