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=-2.3 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 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 205C9C10F14 for ; Tue, 8 Oct 2019 17:00:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id EC7CD2070B for ; Tue, 8 Oct 2019 17:00:24 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=kernel-dk.20150623.gappssmtp.com header.i=@kernel-dk.20150623.gappssmtp.com header.b="gB1e0Pwf" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729790AbfJHRAY (ORCPT ); Tue, 8 Oct 2019 13:00:24 -0400 Received: from mail-io1-f68.google.com ([209.85.166.68]:38441 "EHLO mail-io1-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725917AbfJHRAX (ORCPT ); Tue, 8 Oct 2019 13:00:23 -0400 Received: by mail-io1-f68.google.com with SMTP id u8so38075130iom.5 for ; Tue, 08 Oct 2019 10:00:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel-dk.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=jjX9NlOHpquC/Sfta8LEcd2OkeJi//hJzKxsmDBzbTE=; b=gB1e0PwfuyEBf0jsz8o+5nHpb3VXP4nLO2wfWhWGC/75vX90xaUYLZ4CufQ5pwgEWA f8a5GGESkScrhfUAFIM4IFRh3V0WAhqgs+Kmk3mWHKL2rEcI8HlIY1LfgTOQlCc6tP0b h6jT5o5L+wV1miWcBWTMdBUybHf6EcVoGjHdL13bcBnoLCFVA7KP3/9aIKvJX2MQkxAr KYwxpGBGlnQ94spt/znvnB8E6DmZI+mw4LA5Oa6tJhfgzhsDywolVaDeuQ3f/MFzOt/d 1Xug10qjK5BsETha8IW6lHS6mIO8JkOX/87sj4GVcyu7dCn/AzcS+9IUP00iMTOvuWoK IKPw== 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=jjX9NlOHpquC/Sfta8LEcd2OkeJi//hJzKxsmDBzbTE=; b=UmSH1QKn7ESguWrzNa3d5aXCnKxy1WIPn8wB0HHk/510JgfUHQl2kO2MritEsP5NTI 0rwkocvIgrVAJ8SADO5HeuYSlujxaMn7phCtdQUjyNtoeIhvG3TtubczWJrYGPd5mSIS /JVhohbxP440ze7RdOPRlm0R/uMOpDqq2NPScJGSvz4uoe1oB+zpgJXLeWW818rb324O 0PdzeSN7cHLQJ2EzDBfgzoCrixlS2mpfJtUJwK+I8cdW2so68J3pHAx0rbih/B2tIlgB d3zdsQtvFwEpjJoOZlpWXqTvUJIKbUDbo1odV58MZuR3g9X8DD+OFw2LXpXXQTGVnwjY UF7Q== X-Gm-Message-State: APjAAAW0R3Rf8rpYSXpVyMZqXYKHqOWkMJHs9kln+UoruXpJ3V1XqX8R XEEp7Zi02eMYNRQoJrJFD/up8EykOcF1rQ== X-Google-Smtp-Source: APXvYqwAmqmBluQAIhWf2f/0FiXxNwozNzClbWMkH8dbk0HE2IO35d/M6WcDFO4TLIqY5dwZ5O2cxg== X-Received: by 2002:a5d:9c4c:: with SMTP id 12mr29014127iof.276.1570554022169; Tue, 08 Oct 2019 10:00:22 -0700 (PDT) Received: from [192.168.1.50] ([65.144.74.34]) by smtp.gmail.com with ESMTPSA id r2sm9402226ila.52.2019.10.08.10.00.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 08 Oct 2019 10:00:20 -0700 (PDT) Subject: Re: [PATCH] io_uring: remove wait loop spurious wakeups To: Pavel Begunkov , linux-block@vger.kernel.org, linux-kernel@vger.kernel.org References: <936cd758d6c694fe1b8b9de050e24cfecdc2e60d.1570489620.git.asml.silence@gmail.com> From: Jens Axboe Message-ID: <62a8a6c7-9c5b-c9a4-9c73-c77db87c6637@kernel.dk> Date: Tue, 8 Oct 2019 11:00:19 -0600 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: 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 10/8/19 10:43 AM, Pavel Begunkov wrote: > On 08/10/2019 06:16, Jens Axboe wrote: >> On 10/7/19 5:18 PM, Pavel Begunkov (Silence) wrote: >>> From: Pavel Begunkov >>> >>> Any changes interesting to tasks waiting in io_cqring_wait() are >>> commited with io_cqring_ev_posted(). However, io_ring_drop_ctx_refs() >>> also tries to do that but with no reason, that means spurious wakeups >>> every io_free_req() and io_uring_enter(). >>> >>> Just use percpu_ref_put() instead. >> >> Looks good, this is a leftover from when the ctx teardown used >> the waitqueue as well. >> > BTW, is there a reason for ref-counting in struct io_kiocb? I understand > the idea behind submission reference, but don't see any actual part > needing it. In short, it's to prevent the completion running before we're done with the iocb on the submission side. > Tested with another ref-counting patch and got +5-8% to > nops performance. > > -- Jens Axboe