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 X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1D130C433ED for ; Tue, 20 Apr 2021 20:33:38 +0000 (UTC) Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id A01B1613C0 for ; Tue, 20 Apr 2021 20:33:37 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org A01B1613C0 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=fooishbar.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=dri-devel-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id C825D6E8C7; Tue, 20 Apr 2021 20:33:36 +0000 (UTC) Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) by gabe.freedesktop.org (Postfix) with ESMTPS id 6135C6E8C7 for ; Tue, 20 Apr 2021 20:33:36 +0000 (UTC) Received: by mail-wm1-x32b.google.com with SMTP id t14-20020a05600c198eb029012eeb3edfaeso32743wmq.2 for ; Tue, 20 Apr 2021 13:33:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fooishbar-org.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Dot1S2WUXdDAJy8DTSBlbUGNbczdrI5EBdPQfEViNNY=; b=Xqda/YYoD+EQcVXHE3NhjtclB46r0QnI3sYGif9B+P7gjbiyRLCjCE/yHzUUasBpMR rljpJH4IsDXVtRf7bh2a2EnAarKd3oa5KDRgPOJx0yr9yfKC+AvOzHugE8CT7RkMmTBd hg0YTnLh/gO03knxjWAQ8HCwJX/TcfMmK4R7jnxei3T1U8IyzE9LxGDiXTNPNxqn9sNN gK+MTexcuLeTZKXkHbOER3n4u/OR6uBWd5DjI9+dUhJfveaufI44XVnfdj0Z6AiirvS6 KQng72ow8s/EdEe+N9ZMbQGf/TxqKS9kJXLdLpL881pBuphndMj3Lcf9SKreMaSvCoj3 FHRg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Dot1S2WUXdDAJy8DTSBlbUGNbczdrI5EBdPQfEViNNY=; b=EvCUPluIp4me7AtGnqJACv1n+mXxMGneB7VI77Sz5a832Qo1RXYxoIWFNrN7a2iu8M ydksicgfd0g26j2fI6EBpj+EV791PIBcz6jVyEXuNVbv8oGor6/7lHVA9ePZObK7zsSg FCAf5+jpk521GHhaPr8RUkUP4Ap0IWrqHLlzRBT17UsNmvM9vekagpghF5VsTD7ayUlj 2EgmqcJQcX5eOA1NgmXFol/3TwVU7izFM0nIoKTBU3fUG5l3IVlwpr4k6M+f9LBuKddi A6E18lv3tWqdK1sMOazGX77QxvIWQGFJ4dWCr0cFdtaB3dGSdfh6kCuPp2eqRZd6LzRG KL/Q== X-Gm-Message-State: AOAM533qHvn5mQeJoe37oZ1Sc0We9T8pBjrB5E8uTxdf/pSNMas4jWuh L8ahBNeVRGGkYkhDPRaw0TdIXppGYvVK8c1t4ySm6w== X-Google-Smtp-Source: ABdhPJzCViC5+Pj9awNnIyaNZesTt//053z5unM20FUpANqn5HCNlgXN4CKct9S7ywPcC8mhQnfnjfSRBQeVU3t0HWc= X-Received: by 2002:a7b:cd98:: with SMTP id y24mr6168114wmj.52.1618950815040; Tue, 20 Apr 2021 13:33:35 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Daniel Stone Date: Tue, 20 Apr 2021 21:32:47 +0100 Message-ID: Subject: Re: [Mesa-dev] [RFC] Linux Graphics Next: Explicit fences everywhere and no BO fences - initial proposal To: Daniel Vetter X-BeenThere: dri-devel@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Direct Rendering Infrastructure - Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: ML Mesa-dev , dri-devel , Jason Ekstrand Content-Type: multipart/mixed; boundary="===============1734018502==" Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" --===============1734018502== Content-Type: multipart/alternative; boundary="0000000000003d5cda05c06d5c54" --0000000000003d5cda05c06d5c54 Content-Type: text/plain; charset="UTF-8" Hi, On Tue, 20 Apr 2021 at 20:30, Daniel Vetter wrote: > The thing is, you can't do this in drm/scheduler. At least not without > splitting up the dma_fence in the kernel into separate memory fences > and sync fences I'm starting to think this thread needs its own glossary ... I propose we use 'residency fence' for execution fences which enact memory-residency operations, e.g. faulting in a page ultimately depending on GPU work retiring. And 'value fence' for the pure-userspace model suggested by timeline semaphores, i.e. fences being (*addr == val) rather than being able to look at ctx seqno. Cheers, Daniel --0000000000003d5cda05c06d5c54 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

<= div dir=3D"ltr" class=3D"gmail_attr">On Tue, 20 Apr 2021 at 20:30, Daniel V= etter <daniel@ffwll.ch> wrote:=
The thing is, y= ou can't do this in drm/scheduler. At least not without
splitting up the dma_fence in the kernel into separate memory fences
and sync fences
=C2=A0
I'm = starting to think this thread needs its own glossary ...
<= span style=3D"">
I propose we use = 9;residency fence' for execution fences which enact memory-residency op= erations, e.g. faulting in a page ultimately depending on GPU work retiring= .

= And 'value fence' for the pure-userspace model suggested by timelin= e semaphores, i.e. fences being (*addr =3D=3D val) rather than being able t= o look at ctx seqno.

Cheers,
Daniel<= /div>
--0000000000003d5cda05c06d5c54-- --===============1734018502== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel --===============1734018502==--