From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 369D4C6FD1D for ; Wed, 15 Mar 2023 21:09:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232860AbjCOVJO (ORCPT ); Wed, 15 Mar 2023 17:09:14 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49190 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231791AbjCOVJC (ORCPT ); Wed, 15 Mar 2023 17:09:02 -0400 Received: from mail-io1-xd2c.google.com (mail-io1-xd2c.google.com [IPv6:2607:f8b0:4864:20::d2c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1CEC38A55 for ; Wed, 15 Mar 2023 14:08:49 -0700 (PDT) Received: by mail-io1-xd2c.google.com with SMTP id o14so2873022ioa.3 for ; Wed, 15 Mar 2023 14:08:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20210112.gappssmtp.com; s=20210112; t=1678914528; x=1681506528; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=fN7hOg0hyD5Uv2gg8ttIpEpN6wysp44Fx0ar0ZCj2b8=; b=Q2FoxcRYKL78nJ2C5MFiVvR8QSE3X6bSbLMYxC7lxGiMol3E/CwJOygoDx9yq2q6Za Mk04iWk6ACNuCvrjUiOBIo+lgtaJhwI4/6xLfaTi1Z9K90/5LFl6W4Dscop6VKKHIm8t a/DU384gr2B9N5AdppLLEqW2WnTtrH/NpYvTqRx6fibuIxblOCzgtCRlQK0um+v3Pmsl tVA24y6JsZGlAjFEm5JMwB0CCA3kocKKzC0KRVjonRJ+o1SVByzSE9180PtCxwxYT5FE JEZSe3S7wL+u919u8xb1zCjfgVl2H9dApRzIjDLDQcj4PoSp3awgdegtctZW8WLWg/DO hvrQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678914528; x=1681506528; h=content-transfer-encoding:in-reply-to:from:references: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=fN7hOg0hyD5Uv2gg8ttIpEpN6wysp44Fx0ar0ZCj2b8=; b=774BD8r80m/0rc7u1oIP/M4tUSAy+HodY0Qq/SYIChU3uE6v+tm5X2CAKArKHs9n9P zVnX4cU9Y1QKmXhqJnyRzbJ+WsnOXEAUzM06eQkAM8B4BTJan/kGYPW9Nbu1TR1eQ5CM i/huNyNHnFD7oQHBf/HdW1dV7M5eD+ifxUg6NaFAbT5h7OH6t2zESM/nINn65pvs6vD2 SO2z383ZCbGTyr9XXtZ21Z3XDpk6b06FEO1SSFGB1QfBsnP9ePxWQQaVJKCkvRvlEULO 9sa69x7+TeM6zO1NhMLnXTY+BxTmo0Dj3veSHmJY8s3picqNhHou2/bhRSAtQq+QuLDZ ry0Q== X-Gm-Message-State: AO0yUKWsbqVKi2hfxPSaMSGtQK3nd9W4zL68RuP0KIOStxmd4iIFTMFC QDiIBYfvN+QmGbZh6jPXrHmt/A== X-Google-Smtp-Source: AK7set+FYNEe1T/s9a1r0Oz1xnXYdBB/53tjQyOWVbt+D1su7gQm+eqsOrVhBL8a9Wr6r5TPuH+NuQ== X-Received: by 2002:a6b:14d2:0:b0:72c:f57a:a37b with SMTP id 201-20020a6b14d2000000b0072cf57aa37bmr2371735iou.2.1678914528424; Wed, 15 Mar 2023 14:08:48 -0700 (PDT) Received: from [192.168.1.94] ([96.43.243.2]) by smtp.gmail.com with ESMTPSA id k23-20020a5d97d7000000b00740694b5f43sm1977480ios.46.2023.03.15.14.08.47 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 15 Mar 2023 14:08:48 -0700 (PDT) Message-ID: <4b09b903-ffed-8fc7-482a-eabcf152c98b@kernel.dk> Date: Wed, 15 Mar 2023 15:08:47 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [PATCHSET 0/5] User mapped provided buffer rings Content-Language: en-US To: John David Anglin , Helge Deller , io-uring@vger.kernel.org, linux-parisc References: <20230314171641.10542-1-axboe@kernel.dk> <0eeed691-9ea1-9516-c403-5ba22554f8e7@gmx.de> <3dcf3e0c-d393-cb95-86ab-00b4d8cf3c75@gmx.de> <88b273f6-a747-7d2e-7981-3d224fdac7be@kernel.dk> <19dcf149-9ee7-048e-193c-accf297d7072@bell.net> From: Jens Axboe In-Reply-To: <19dcf149-9ee7-048e-193c-accf297d7072@bell.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-parisc@vger.kernel.org On 3/15/23 3:04?PM, John David Anglin wrote: > On 2023-03-15 4:38 p.m., Jens Axboe wrote: >> For file-verify.t, that one should work with the current tree. The issue >> there is the use of registered buffers, and I added a parisc hack for >> that. Maybe it's too specific to the PA8900 (the 128 byte stride). If >> your tree does have: > The 128 byte stride is only used on PA8800 and PA8900 processors. Other PA 2.0 processors > use a 64 byte stride. PA 1.1 processors need a 32 byte stride. > > The following gcc defines are available: _PA_RISC2_0, _PA_RISC1_1 and _PA_RISC1_0. Ah perfect! > /proc/cpuinfo provides the CPU type but I'm not aware of any easy way to access the stride value > from userspace. It's available from the PDC_CACHE call and it's used in the kernel. model : 9000/785/C8000 - Crestone Peak Mako+ Slow [128] I guess that's why it worked for me. OK, will ponder how to define that, I think just going lowest common denominator is enough for now. -- Jens Axboe