Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp6273333ybi; Wed, 31 Jul 2019 11:19:50 -0700 (PDT) X-Google-Smtp-Source: APXvYqyNw2HKCeS5mxp/v6s6yjXLf/uf3Ca//gZh7LjT/t5Haqf+EaMq2lf0wU1/SSB+XDtB2/SK X-Received: by 2002:a62:1d8f:: with SMTP id d137mr49909377pfd.207.1564597190613; Wed, 31 Jul 2019 11:19:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1564597190; cv=none; d=google.com; s=arc-20160816; b=dJ4fh5GyQD1DNedv3EM6uk5PP8vd2J1DV46R4e2BtMT3yv+TMTPxoMJ+Ttcuhko4Ap UVgKwo8J1wUwmYQOCzV6oYJYTSw0meD+C0flFgx3Tc6zIQrq/8KWDBDdHTOlW+T21trF Et+a8BogQyjIDIU++B1UhvMUQiwm6tduMUoAT/h5nf31qD3dtLTkyXhjSI6gY4JtAzP6 U4OlYiFfIaUHYvPU9P3/zSykvLXVFJGHr3cim8aPfgFziuhTlGTNBjw3zg7IRtkxC0p/ Vl9Hz8UZAV/bsSAvNL98ywyNgUBCVsdj7tUSrj432Ny293dQQxpxua+DI916Go9HOjtV uqCQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=8Z0P5Wb3N6RNbSuxVxTxovjy+jlIt5UjpbTJFLTHGvg=; b=JvNxHSKW33h9/CYoIdomXeFWSFFJLa4D8kGIKxAxn8rXIH1BVWA/ar+LmTS96oxS8+ bfN4Q3RdLL53PP6Ho40d3QgrF+Pm62JkZd/EolPjo84nHsbxzOCkTNiMV54DDQ9KhP8v Fx72e9rHNiRSgOgIggsn+zrckZf+qll8LvpbydxXaEp7XBfCFQ3mV8G0KR6AMcJFh3rB //OpBt6faQxEPgohHj409s1uy+aPvigjegScTzWtlYGitw0Goh5ZF0aCjgijXjHepnoN Ssli3cSgN0rJYtvjP9KECu/g+/BvRlldXSy/vVzvffj02ZLVn3Q3k38s8/olzj+B1eiJ 2Ysw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Yl8AqYJN; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i8si1951316pju.32.2019.07.31.11.19.34; Wed, 31 Jul 2019 11:19:50 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=Yl8AqYJN; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728868AbfGaPVg (ORCPT + 99 others); Wed, 31 Jul 2019 11:21:36 -0400 Received: from mail-pf1-f196.google.com ([209.85.210.196]:40597 "EHLO mail-pf1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727264AbfGaPVe (ORCPT ); Wed, 31 Jul 2019 11:21:34 -0400 Received: by mail-pf1-f196.google.com with SMTP id p184so32048733pfp.7 for ; Wed, 31 Jul 2019 08:21:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=8Z0P5Wb3N6RNbSuxVxTxovjy+jlIt5UjpbTJFLTHGvg=; b=Yl8AqYJNSj8Uxqi6ahv+iq+Yf5YGpSzIGgio2doxdbl+ZbJpe2L80fRRMpzBWrHjSo JT2/+vjR5pjbF8HuSpNq+tjQns7I5KyAb6VSFhDyfI6IcRINOXrGX0Sx0+4152EVCKyi QG9CnJOjxyeAkcfsxwU4HM2nM4XLhiz6V/k1TyDO8nIicoOnaPi1q9KOJRYgf5cXpCDD SN0e7PyBSpRf/Xz+PSbwTQ5iYd/P/pK6KQ6Pv9XSpy9LgufVH4mgoSbdwRE89BK5kv7T Ebk/BY7eRL3FwpeM5CHABrx73aJnw/blKmMVxCyhz6czHFJoR5e1ZbmwEgZo0KCTjCd5 2eYQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=8Z0P5Wb3N6RNbSuxVxTxovjy+jlIt5UjpbTJFLTHGvg=; b=OdTYlZqtfoSn3IVGF/ws+R2JUgnVRqHSvEXQ3D0YxqvCjStF8/6zORt2V3Xbxz3V/n i6F4bTOVWJQ9xfYDazx28/5Bp9em1IOid1TUqTt722T3GNeXiIQoBoYXx4vX4vzi60AC DNo7Op9xAXjnNlJI/ahJYakXSa8oqilem55r9skyLkqOh9sbuFZa9DFo1eAtmfaPQ6tl AORw1zfDbHjoSgGNM/tToBEa5tyKLDQYRQ7zAkVTUQtqm4MZlZnS5YsqKMxP01VW6ps7 kCE+BQoQrrC4UTcA/FhC44Ey7f+LC0vp69qVjZClo1H2/hdj2WwqyXT9IkclzpuI9nNM TCbQ== X-Gm-Message-State: APjAAAUQN45xNUsREZooFbDJNwGfdWUqsYCAmFjkIRI2EFH6o5+5QEKr tiDxSQ2D0mXfks11Zb/6N6o= X-Received: by 2002:a17:90a:25af:: with SMTP id k44mr3435781pje.122.1564586151955; Wed, 31 Jul 2019 08:15:51 -0700 (PDT) Received: from [10.69.137.114] ([50.228.72.82]) by smtp.gmail.com with ESMTPSA id c70sm23254601pfb.36.2019.07.31.08.15.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Jul 2019 08:15:51 -0700 (PDT) Subject: Re: [PATCH RFC 2/2] futex: Implement mechanism to wait on any of several futexes To: Peter Zijlstra , Gabriel Krisman Bertazi Cc: tglx@linutronix.de, mingo@redhat.com, dvhart@infradead.org, linux-kernel@vger.kernel.org, kernel@collabora.com, Steven Noonan , "Pierre-Loup A . Griffais" , viro@zeniv.linux.org.uk, jannh@google.com References: <20190730220602.28781-1-krisman@collabora.com> <20190730220602.28781-2-krisman@collabora.com> <20190731120600.GT31381@hirez.programming.kicks-ass.net> From: Zebediah Figura Message-ID: <306b3332-0065-59dc-e6d6-ee3c8a67ef53@gmail.com> Date: Wed, 31 Jul 2019 10:15:49 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <20190731120600.GT31381@hirez.programming.kicks-ass.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 7/31/19 7:06 AM, Peter Zijlstra wrote: > On Tue, Jul 30, 2019 at 06:06:02PM -0400, Gabriel Krisman Bertazi wrote: >> This is a new futex operation, called FUTEX_WAIT_MULTIPLE, which allows >> a thread to wait on several futexes at the same time, and be awoken by >> any of them. In a sense, it implements one of the features that was >> supported by pooling on the old FUTEX_FD interface. >> >> My use case for this operation lies in Wine, where we want to implement >> a similar interface available in Windows, used mainly for event >> handling. The wine folks have an implementation that uses eventfd, but >> it suffers from FD exhaustion (I was told they have application that go >> to the order of multi-milion FDs), and higher CPU utilization. > > So is multi-million the range we expect for @count ? > Not in Wine's case; in fact Wine has a hard limit of 64 synchronization primitives that can be waited on at once (which, with the current user-side code, translates into 65 futexes). The exhaustion just had to do with the number of primitives created; some programs seem to leak them badly.