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=-3.8 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,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 0BCEEC433E2 for ; Wed, 15 Jul 2020 11:05:21 +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 D6E2F206F5 for ; Wed, 15 Jul 2020 11:05:20 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=basnieuwenhuizen-nl.20150623.gappssmtp.com header.i=@basnieuwenhuizen-nl.20150623.gappssmtp.com header.b="Sr5FqN/0" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D6E2F206F5 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=basnieuwenhuizen.nl 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 0C98D6EAA4; Wed, 15 Jul 2020 11:05:20 +0000 (UTC) Received: from mail-il1-x135.google.com (mail-il1-x135.google.com [IPv6:2607:f8b0:4864:20::135]) by gabe.freedesktop.org (Postfix) with ESMTPS id 7E5A56EAA2 for ; Wed, 15 Jul 2020 11:05:18 +0000 (UTC) Received: by mail-il1-x135.google.com with SMTP id q3so1578960ilt.8 for ; Wed, 15 Jul 2020 04:05:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=basnieuwenhuizen-nl.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ouG49VA4xk2vrvpG0VnN69idUXmFZrH/pn1ZmxXpzDU=; b=Sr5FqN/0aOR+KGr5kKNyZvHHas9BR6wkNR5nQSIO13n5K1CIuzqHk3EOk8vKhRUAez 1XcOCU7/Tnq5lsGuMEtBqk4Jm/pXwD4gq00+ga/i0iMSaODmcY4SsEFe1kaxgbNo2g8H DfRHenbLfYihQd0MWJafryvTYt4E/PH0dFOyshcEF/UrflHUcErSk1FKSwWd+zTqfZpR 8TqZoEBg01ZyfslmPjARTDRFqXZM4pb2FIolaOI1zi3tqc4mE+RYta8XH2Tmbswue+py Bvb1X64tI31op9ryGM+/raT3mBNYBK0OZ6MOslFX9W+Qvizrh1Z/DP3so7H+EEbHgICT ENfA== 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=ouG49VA4xk2vrvpG0VnN69idUXmFZrH/pn1ZmxXpzDU=; b=HlmlDTFpQfnKkfY2RzCaFMXKfT/clCDJXPhhgjpOXZMjy38F2h0Kj4qTCYjrLCT5gN zS/cPz5dd5BiWpSfhPvQ9pFGcl8aNRVvhOw1G+m1PrIBr8QhXRto9fU4BNrSf7XQ4Gn6 TeYsxO7PGL4SljMlNuPZybeKBQUSGShx9hxqr7owmybAwiOJ2HPE2YTEvm7PegZuHMWP BuodYmhuqj1ZhxknerSCqam3MDaZiMwK4aVz40zjhMbHGxmy7BV1X94yhqEFHg3tZdhI y/vZ5bf9oXTV3FjyiZARopP4/k5T0NkVdUfubene9lWvWKcowSwitJh8T050xfQqA3JZ g3sQ== X-Gm-Message-State: AOAM530FUsG5NXQbYPRElJbwvaoXtM3lJlUCyrFAgG/vYa52ES0wOgQ3 uzp0eM/7GuYinHwF9Vdu9k5e+7huKWmE8ENgOK7rIA== X-Google-Smtp-Source: ABdhPJzYSTbo8+bXktW4UUhmN9qzR9fploDu1xkeIs5QRM7sQX6kde2xpE9yEtWma280/dlZ4LexdNHEMtHvpzs/u0M= X-Received: by 2002:a92:8b0e:: with SMTP id i14mr8801447ild.307.1594811117684; Wed, 15 Jul 2020 04:05:17 -0700 (PDT) MIME-Version: 1.0 References: <20200715100432.13928-1-chris@chris-wilson.co.uk> <159480926758.13728.809663901463022623@build.alporthouse.com> In-Reply-To: <159480926758.13728.809663901463022623@build.alporthouse.com> From: Bas Nieuwenhuizen Date: Wed, 15 Jul 2020 13:05:06 +0200 Message-ID: Subject: Re: sw_sync deadlock avoidance, take 3 To: Chris Wilson 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: intel-gfx@lists.freedesktop.org, ML dri-devel Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" On Wed, Jul 15, 2020 at 12:34 PM Chris Wilson wrote: > > Quoting Bas Nieuwenhuizen (2020-07-15 11:23:35) > > Hi Chris, > > > > My concern with going in this direction was that we potentially allow > > an application to allocate a lot of kernel memory but not a lot of fds > > by creating lots of fences and then closing the fds but never > > signaling them. Is that not an issue? > > I did look to see if there was a quick way we could couple into the > sync_file release itself to remove the syncpt from the timeline, but > decided that for a debug feature, it wasn't a pressing concern. > > Maybe now is the time to ask: are you using sw_sync outside of > validation? Yes, this is used as part of the Android stack on Chrome OS (need to see if ChromeOS specific, but https://source.android.com/devices/graphics/sync#sync_timeline suggests not) > -Chris _______________________________________________ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel