Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp1108398ybl; Thu, 23 Jan 2020 13:46:50 -0800 (PST) X-Google-Smtp-Source: APXvYqyh9l4fjP2uMfC4EpSpR+Y02RZ9nrgUujPAuU4J4R6YZd99WDc60DHnAJZLYx2YAKMzI24p X-Received: by 2002:a9d:461b:: with SMTP id y27mr394878ote.280.1579816010220; Thu, 23 Jan 2020 13:46:50 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579816010; cv=none; d=google.com; s=arc-20160816; b=XbxKgNuw4WKJfWP0s564sxHGQmmEVzGskHqJPyZv49qnAbDoMgu63Ro8JnFFljez3t YztrzuwKANEcKlLFLJ2CpF0i966hLwsChAjpNlGMjdDljqlz/S8uaCc+XqlXGXPLdV92 UgPhP/8ELgaeH5tBdEAU0WvIVrV68TQnr9Fe/Z8eYhz4ccJ6qhSdvlHxBakZjriPk6Be BZbAbbCIGOVweHjo2C0TUa8pTmnpIBnXKlgQYUfpf+b7wMo5B+tPlcmpxgBLZNV28O+i LOGln6XgIgTxTO8Exp5dWN9BTxB8ruZFoaS6svjmYTW2q1sI1CkrNDp1wKTshmmiDkLd TIqQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=u61jrRml7uBsTChqQkvEyIjmfc5MgOu8Mlxfsu5OMjo=; b=PpejPmF0LquL6frucynLl71jG4IvYd9lp3p5EycfrOSEf1A9QXMCi3eCTZ8o7rNnaI xOr5OII0ePzv+hKxkaMOw9oVNLoQQOwjUzqsfKBHwYrzX453ntTrQYOhUL0aCKXwLl8W RjTpwL085wZc/svMmG7jy/FYRil2sX7ANdLk1L0gcArhQJ1EUNqS+E4IJ3HQiOEB9Kul 9iDMDBRIkwVgKJoRj3e0PJfguMm0j4ag3XPJfUM6yy4rRHCk64bPsKhOU7wHYCu0KZNt F24bVTuaQgXW4VALF6npdc22swj1v1TwDoGmN2UDOxS9DIog5Rz5FbuY71mHWwaTMTmB aWeg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=LGYaj3ag; 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=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l204si1375818oif.261.2020.01.23.13.46.38; Thu, 23 Jan 2020 13:46:50 -0800 (PST) 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=@redhat.com header.s=mimecast20190719 header.b=LGYaj3ag; 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=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729122AbgAWVpm (ORCPT + 99 others); Thu, 23 Jan 2020 16:45:42 -0500 Received: from us-smtp-delivery-1.mimecast.com ([205.139.110.120]:48493 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728911AbgAWVpl (ORCPT ); Thu, 23 Jan 2020 16:45:41 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1579815940; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=u61jrRml7uBsTChqQkvEyIjmfc5MgOu8Mlxfsu5OMjo=; b=LGYaj3ageoOgOQJYg/Wlyy3OIhnOdZumeDj/G8cRfAEWZzQYax/8aBrpah5R2zMyNAyvEZ qCYBMg+MDpse+Np4GbrmyTskgvB1JqaHlMQG/BUIA9AsmNcj1lJZnXIYT7Muu2HzKLrl67 x6gowANcsZJ4FtrJ1Bya6KtZRzdBg10= Received: from mail-wm1-f71.google.com (mail-wm1-f71.google.com [209.85.128.71]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-356-m_EnMrTeMc-3suXy6w0IHg-1; Thu, 23 Jan 2020 16:45:38 -0500 X-MC-Unique: m_EnMrTeMc-3suXy6w0IHg-1 Received: by mail-wm1-f71.google.com with SMTP id y24so1697382wmj.8 for ; Thu, 23 Jan 2020 13:45:38 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=u61jrRml7uBsTChqQkvEyIjmfc5MgOu8Mlxfsu5OMjo=; b=a3UIsDBKdfAszgk4MOxJxGlNHL2Cbm+TONTtaJS61XZf/lTPlNyezNGwm86jwaRlhZ hdDcDk6xaUyu3FPYZv/+NL3aXBetK3pj+/Zxwup+10cs6vIadM8RE0zoMAWy5lueHmrp aQUC8/LB9LC805GyV0F+69HUuH977ZlXlwj4VY6XMJ5mw3v2NTAYbvHMViiHL/TBKbel wh1uLbao5Q8jhUHUid+1Jtr25sPk6UONoq/90OI9A3YD2fSB4Pl4uWpPOnZfmIzSN0ZP 1JBt9Ja8MqxmFRzoeVTlXa4TxmlLAGx4WYbX5ALYziaJmOqrIwa2RkuVsJ6BLfyTlz9Z 04uQ== X-Gm-Message-State: APjAAAUzOXqxF2931sV6QN123Nbmp0K2KHJF+ui6rJ+8Ks6ZxWZ27LNe hHbgPn4w7LBh5EsRMXSTz1sqOM41xRbseC153FnS6/n0xNORmLa4Dyy9kOiANkFDERl2Q5B0+WQ LlmhifIUbrHYSpmyzJkOVFzeg X-Received: by 2002:a5d:4085:: with SMTP id o5mr91673wrp.321.1579815937023; Thu, 23 Jan 2020 13:45:37 -0800 (PST) X-Received: by 2002:a5d:4085:: with SMTP id o5mr91651wrp.321.1579815936765; Thu, 23 Jan 2020 13:45:36 -0800 (PST) Received: from steredhat ([80.188.125.198]) by smtp.gmail.com with ESMTPSA id y139sm4299842wmd.24.2020.01.23.13.45.35 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 23 Jan 2020 13:45:35 -0800 (PST) Date: Thu, 23 Jan 2020 22:45:33 +0100 From: Stefano Garzarella To: Jens Axboe Cc: Alexander Viro , io-uring@vger.kernel.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: Re: [PATCH] io_uring: wakeup threads waiting for EPOLLOUT events Message-ID: <20200123214533.ikn4olf7k5dfbaq6@steredhat> References: <20200116134946.184711-1-sgarzare@redhat.com> <2d2dda92-3c50-ee62-5ffe-0589d4c8fc0d@kernel.dk> <20200116155557.mwjc7vu33xespiag@steredhat> <5723453a-9326-e954-978e-910b8b495b38@kernel.dk> <20200116162630.6r3xc55kdyyq5tvz@steredhat> <20200116170342.4jvkhbbw4x6z3txn@steredhat> <2d3d4932-8894-6969-4006-25141ca1286e@kernel.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2d3d4932-8894-6969-4006-25141ca1286e@kernel.dk> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 23, 2020 at 12:13:57PM -0700, Jens Axboe wrote: > On 1/16/20 10:03 AM, Stefano Garzarella wrote: > > On Thu, Jan 16, 2020 at 09:30:12AM -0700, Jens Axboe wrote: > >> On 1/16/20 9:26 AM, Stefano Garzarella wrote: > >>>> Since the use case is mostly single submitter, unless you're doing > >>>> something funky or unusual, you're not going to be needing POLLOUT ever. > >>> > >>> The case that I had in mind was with kernel side polling enabled and > >>> a single submitter that can use epoll() to wait free slots in the SQ > >>> ring. (I don't have a test, maybe I can write one...) > >> > >> Right, I think that's the only use case where it makes sense, because > >> you have someone else draining the sq side for you. A test case would > >> indeed be nice, liburing has a good arsenal of test cases and this would > >> be a good addition! > > > > Sure, I'll send a test to liburing for this case! > > Gentle ping on the test case :-) > Yes, you are right :-) I was a little busy this week to finish some works before DevConf. I hope to work on the test case these days, so by Monday I hope I have it ;-) Cheers, Stefano