Received: by 2002:a25:c205:0:0:0:0:0 with SMTP id s5csp2376910ybf; Mon, 2 Mar 2020 07:27:29 -0800 (PST) X-Google-Smtp-Source: ADFU+vt5nhBwMv+jUvPmSFfx3z/KFliucTKew0ahQE1dIdTsDvnMwiMl/OQX7BasMKSkWV+uJyL7 X-Received: by 2002:aca:43c1:: with SMTP id q184mr31568oia.116.1583162849680; Mon, 02 Mar 2020 07:27:29 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1583162849; cv=none; d=google.com; s=arc-20160816; b=vkMHYMeb7h53HCaHFpyDN+P8SpGmkp7pXsY/5koCqPQiG2x/nJI9PJgHKBdwoxDzXR nwQ46jt+lvm3YA5ABOxEdLxxbz1xXDLjAHSPUTbCmJxvKsrECpHZUA/Snmj7fr/WqXQS tfdnyArPHe2VnXbpVS7LWOxE+TCt7OZEkKU1wafWHVdvjjykNfDAX+QvIGej+wWLZBV7 m3vYrBFpPWEJ4g+rSOgp88HEmMS2kuRUEWweg0+FDodWN2P+eJn9/4GM0oZSnr7G2GPN FrVes4KM8PFGvn+G5Locj2od9zsHU5Mb5vatHhJtaUczTGVbCSsnN2JMs4i/4B/SmLFv 3fvA== 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:to:subject:dkim-signature; bh=bukTu9hwl5g5tnxxRv26V6s76cWTVObhbh4EskdLihU=; b=M43m0P68B04mY5R1TxuuXgaNM7Zuq+lFKWHSmFBa3pKFEZad8rNRPyFY0wwh87AD/E eNfdvXqiqVCHGn2FB1hG2MhiVEOrjIYa6equwUFoAo09aUt5etYNWHJHsu2yybjuk1Yb /So2OjgZav3SSz0z5IiA97Ktax46LMGwM9KMJOw3yU8pTEDe1lJ/PR8Qs4n+Y8h18uYI o/198rymBs+uMrOkGIku3OizLf5C9BfSeaLl0ea8ZepO49p/1EiUHjYRft7pSHnQYJeP tC0k+s9799m6r6GP5jjHZAJenBj4Uuy37folXYDL75zjnchli7/0wX3ixCtZ3ifDdDgH zNPQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=OoSkkwh7; 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 v3si6764266otn.140.2020.03.02.07.27.17; Mon, 02 Mar 2020 07:27:29 -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=@gmail.com header.s=20161025 header.b=OoSkkwh7; 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 S1727305AbgCBP0F (ORCPT + 99 others); Mon, 2 Mar 2020 10:26:05 -0500 Received: from mail-lf1-f67.google.com ([209.85.167.67]:36121 "EHLO mail-lf1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726805AbgCBP0F (ORCPT ); Mon, 2 Mar 2020 10:26:05 -0500 Received: by mail-lf1-f67.google.com with SMTP id s1so7922480lfd.3; Mon, 02 Mar 2020 07:26:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=bukTu9hwl5g5tnxxRv26V6s76cWTVObhbh4EskdLihU=; b=OoSkkwh7Cmv3dCPJ/k1vu9Sn5CeBGuir/88pWzCGEYK9jq7EjoUY7/PBZmMJMtmxYg M5wWnf3WOrg76bbA8+VQsuj8mj+RbK8UMLq7PR7yIx3LE6+WR3Qn3aO0B3/hMgX3osbS a5A3V/GeBRDKnR4zfzy7DoWCALYlD07R6nlmwtF6t0GKYjoEdmqcd5D5Eq/Ft8YmEW7o T3QKXKNkhGaPw8hmO+5+OJwDLIYWPREuQarcV4clbrOyR0qz0wo0VOHt4Lss8b2wxfhj 2F1APIe4aPffFjqqZsd88CVqULmVOxY6U+PxKWHp6JUQcpN9ItxqMzVeMyctKqSlfYF6 WKEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=bukTu9hwl5g5tnxxRv26V6s76cWTVObhbh4EskdLihU=; b=TSuxY52FDcs2u4vg+c0FYTjHJTGY0YtTjzaKPqTRTa4U3LcnYp/nFibix3qE7esJtl lKUU1av7xx6AS/AgJIF//1Gb4g8gFCjZR/68DRTp5bzrnNAKO4iGbdnd7gA+ngYKOFVm VkE1OPa1a5dWXOSLDVLC1wOhdJzTlqNc4SpJFXRtUNvGQIUaAe5hVpPkg69PuIIzP/9f m91ldvj+B/zNbfgHlsjo6jMtvMhmU00QQi1Jv9s3uTEgPNEdS3qVQlYh7KWwNJcDXxVW xlggwzLNt1bOPRA/F8GO5eyyR+w93QNbQK0b+mLiNYcFdQFaBs7+3UCddxNB2+9DXnhU vKbw== X-Gm-Message-State: ANhLgQ3PBBJZApPBGdxikNpkW0tDuqYvqB6TBuDYoOFMtGEgjir5DzX8 K0Qy8pusXqp2JAt2qSCdUnF0ichNx8E= X-Received: by 2002:a19:ed08:: with SMTP id y8mr11146164lfy.56.1583162762468; Mon, 02 Mar 2020 07:26:02 -0800 (PST) Received: from [172.31.190.83] ([86.57.146.226]) by smtp.gmail.com with ESMTPSA id 138sm12353615lfk.9.2020.03.02.07.26.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 02 Mar 2020 07:26:01 -0800 (PST) Subject: Re: [PATCH 9/9] io_uring: pass submission ref to async To: Jens Axboe , io-uring@vger.kernel.org, linux-kernel@vger.kernel.org References: <29efa25e63ea86b9b038fff202a5f7423b5482c8.1583078091.git.asml.silence@gmail.com> <902c439f-81ff-7593-e6b4-eee3f217c292@kernel.dk> From: Pavel Begunkov Message-ID: <19a08aaa-069b-27d1-1cb7-5033b74c2e78@gmail.com> Date: Mon, 2 Mar 2020 18:26:01 +0300 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: <902c439f-81ff-7593-e6b4-eee3f217c292@kernel.dk> Content-Type: text/plain; charset=utf-8 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 3/2/2020 6:12 PM, Jens Axboe wrote: > On 3/2/20 8:08 AM, Pavel Begunkov wrote: >> On 3/2/2020 12:39 AM, Pavel Begunkov wrote: >>> On 01/03/2020 19:18, Pavel Begunkov wrote: >>>> Currenlty, every async work handler accepts a submission reference, >>>> which it should put. Also there is a reference grabbed in io_get_work() >>>> and dropped in io_put_work(). This patch merge them together. >>>> >>>> - So, ownership of the submission reference passed to io-wq, and it'll >>>> be put in io_put_work(). >>>> - io_get_put() doesn't take a ref now and so deleted. >>>> - async handlers don't put the submission ref anymore. >>>> - make cancellation bits of io-wq to call {get,put}_work() handlers >>> >>> Hmm, it makes them more like {init,fini}_work() and unbalanced/unpaired. May be >>> no a desirable thing. >> >> Any objections against replacing {get,put}_work() with >> io_finilise_work()? It will be called once and only once, and a work >> must not go away until it happened. It will be enough for now, but not >> sure whether you have some plans for this get/put pinning. > > I have no further plans there, the get/put work only exist to ensure that > the work item stays valid in case of cancelation lookups. Great, it'll go into v2 as well. -- Pavel Begunkov