From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pj1-x102a.google.com (mail-pj1-x102a.google.com [IPv6:2607:f8b0:4864:20::102a]) by sourceware.org (Postfix) with ESMTPS id 27A583858CDA for ; Thu, 30 Mar 2023 06:20:52 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 27A583858CDA Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=gmail.com Received: by mail-pj1-x102a.google.com with SMTP id h12-20020a17090aea8c00b0023d1311fab3so18580496pjz.1 for ; Wed, 29 Mar 2023 23:20:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680157251; x=1682749251; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=85d5aNQxVs5ZJi+eO2D1cOZgeMEwE4Mb1Fqaj8LhuJQ=; b=ESzZQ16/83fEDQ11jfhzGWxCUO2TBC/voudwN5rnbgKvy2hRmftNfttgsjcEsyEjad F6D/9CI+H0G+AFLYedLLu9LdkXdtdvMB+BZ226fflPXu2b724dpihDPiiGht/nxCkUhR L9mGB0UjTzSDouQeeZjHPBWR9DwQ7ivpRlBSu2A2fZm9Tm8T/z2CTKLTY4ITHI0StU5j okk4WAYkGONRnJGgzXDm7mMObc4hCrh/OaOQcuXNm46Oui3/bmt49Z1lRUrnqV4NJN6N pnM/4odo0oY/ilOeD0bPcu66lTXzrL+ryFrLadAqZc2vE5D1DcDEJaihH01jHifbQ1PE JG8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680157251; x=1682749251; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=85d5aNQxVs5ZJi+eO2D1cOZgeMEwE4Mb1Fqaj8LhuJQ=; b=4ZGfj8Oxei5wbbhEiE3VI0Vlpgfj9k1jFQsWty1kDwxx2J+z08AIeVSj8ItgkYd+97 vM9VVCFTSIPCK958Xa/y+3AHicudtdkj98B04sQgZgIrl0iPI+XF7O/+0vnOA5nr2U+J iPGO0lu2t2i6aBy2FPrzSpbEG0SCk00B/6Mcs3Dm69hZwmaq5GrE36FlAb8bMCF0IcRo d/6NLqDovlu2HsRNyEpjZZNd0WyN7i/2zKdIutTZlvmhDZt+SUPtk2EKKPdeU+LgLXkV MK//wTLBKbjwzeW3TUDxBgZYXIEwM8WaXiQM/w6R6Q6hSeEWwTdI5cY6uTvmZWaOBlHK YEdg== X-Gm-Message-State: AAQBX9f3YGOPG/1OMklkfiiObCrGULkHb26Hpx9S/XY7cnJZq8GaaTvD +xQZN8qY0OClu68+B7GXlvefFhDpwXk= X-Google-Smtp-Source: AKy350ZBG0I68Dci+C/txwqVOEipbJVPf59KNZH75L+VXV8lx90nekEYJIOONcZuPL7IIVO4aIL+fw== X-Received: by 2002:a17:90b:1b4a:b0:23f:990d:b5b1 with SMTP id nv10-20020a17090b1b4a00b0023f990db5b1mr24322137pjb.46.1680157251019; Wed, 29 Mar 2023 23:20:51 -0700 (PDT) Received: from ?IPV6:2601:681:8600:13d0::f0a? ([2601:681:8600:13d0::f0a]) by smtp.gmail.com with ESMTPSA id w9-20020a17090a028900b0023c8a23005asm2364969pja.49.2023.03.29.23.20.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 29 Mar 2023 23:20:50 -0700 (PDT) Message-ID: <9290df69-8946-3b67-63ea-3d386a3c30a6@gmail.com> Date: Thu, 30 Mar 2023 00:20:48 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0 Subject: Re: [PATCH v2 0/3] RISC-V: ifunced memcpy using new kernel hwprobe interface Content-Language: en-US To: Palmer Dabbelt , adhemerval.zanella@linaro.org Cc: Evan Green , libc-alpha@sourceware.org, slewis@rivosinc.com, Vineet Gupta References: From: Jeff Law In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.3 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,NICE_REPLY_A,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On 3/29/23 13:45, Palmer Dabbelt wrote: > It's not in for-next yet, but various patch sets / proposals have been > on the lists for a few months and it seems like discussion on the kernel > side has pretty much died down.  That's why I was pinging the glibc side > of things, if anyone here has comments on the interface then it's time > to chime in.  If there's no comments then we're likely to end up with > this in the next release (so queue into for-next soon, Linus' master in > a month or so). Right. And I've suggested that we at least try to settle on the various mem* and str* implementations independently of the kernel->glibc interface question. I don't much care how we break down the problem of selecting implementations, just that we get started. That can and probably should be happening in parallel with the kernel->glibc API work. I've got some performance testing to do in this space (primarily of the VRULL implementations). It's just going to take a long time to get the data. And that implementation probably needs some revamping after all the work on the mem* and str* infrastructure that landed earlier this year. jeff