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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id C59E6C77B78 for ; Wed, 3 May 2023 17:04:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229886AbjECREb (ORCPT ); Wed, 3 May 2023 13:04:31 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42620 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229892AbjECRE1 (ORCPT ); Wed, 3 May 2023 13:04:27 -0400 Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B66517A80 for ; Wed, 3 May 2023 10:04:00 -0700 (PDT) Received: by mail-wm1-x32d.google.com with SMTP id 5b1f17b1804b1-3f315712406so33630185e9.0 for ; Wed, 03 May 2023 10:03:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683133438; x=1685725438; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=mmMl2VMIEsTZ9LRsWkbtsMx6QFBJFMfFFed/BURjL0o=; b=ZcgTLZLuwz727c5eo9GeBGNS5yK6YVcIv30/iKtw58u+vTj2nvE7Sf6omyb0xQJ7MZ vx3cS4xLUeP0UEAPT1hjgIvw0NssOs5q4qJL6cWrZRCFU1cQxGv0JV3xt4ltK8TYD6Oo OSZMKX6bLdqyJZyQlUWA0YPg538Auv9Z+2w8HdhP4Ieysk7ZDqiyCqjpJnNIda35IK3x jGov9RYz5HTk75odFPTVm+nja5wFW3H0dPpOj5p7I8Z2YrQAEuodWs9KaiaERsY4B2E/ RMoJtvfKejedWsGyn8dVfxJbA1dTy2KovggfjcuTjTuVmq4omjJN2LOwQRYjfhoHHuj7 604w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683133438; x=1685725438; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=mmMl2VMIEsTZ9LRsWkbtsMx6QFBJFMfFFed/BURjL0o=; b=bZQjO3ibXsjxjm+6bDvLBkJ4gssO+iwtlCSE4JO/HVPgDTbqe1XCgImT858hdUWG0S nG6xf4qKUwjYU2Xts3N0iFhAduPnOL/dIkazDREO/NCrz9iO5PZTzQQSNXs+I0EexaDv PjfNzhcsunnsXUzx+ecWjwGgkKzokQI7EMN2m5gEayZ1NgJUHcxukGdvTXVQ1FE+Yp/t fPCyPL0wkSxvdvUvO9fY0Bm24lnvA9b2wzF57Jpa0RyCBqXZbGuBq0mHY+SmDfZWGhaL mtQXfqRiojE5SVEkcfHLRDEs+rD8gzQRFIKD4tJrcCcSbFd+K9GeRrf7K+I9jEa2Zzsf FtPA== X-Gm-Message-State: AC+VfDwjr2MI2W9wZejziCFL7yiG689Ef8pCD+zdiAbadzw0SBgy3Ub+ WSvKQ64mVMTEibKMv7zb7o9La1gKCCE= X-Google-Smtp-Source: ACHHUZ4HtKRDX3doKMKEXqtL+NXTb9KLGEuE0MEEnmrAunakiZytHSh+Fvrzpzh/dzxo3u4y1BjSvQ== X-Received: by 2002:a05:600c:3b9c:b0:3f1:73d3:5362 with SMTP id n28-20020a05600c3b9c00b003f173d35362mr1976518wms.13.1683133438295; Wed, 03 May 2023 10:03:58 -0700 (PDT) Received: from asus5775.alejandro-colomar.es ([170.253.51.134]) by smtp.googlemail.com with ESMTPSA id l9-20020a1c7909000000b003f193d7c6b7sm2376091wme.41.2023.05.03.10.03.57 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 03 May 2023 10:03:57 -0700 (PDT) From: Alejandro Colomar X-Google-Original-From: Alejandro Colomar To: linux-man@vger.kernel.org, a.clayton@nginx.com Cc: Alejandro Colomar , andrew@digital-domain.net, Alejandro Colomar Subject: [PATCH 2/3] sched_yield.2: NOTES: Remove misleading sentence Date: Wed, 3 May 2023 19:03:52 +0200 Message-Id: <20230503170353.25998-3-alx@kernel.org> X-Mailer: git-send-email 2.40.1 In-Reply-To: <20230503170353.25998-1-alx@kernel.org> References: <20230503170353.25998-1-alx@kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-man@vger.kernel.org sched_yield(2) is not the right thing for heavily contended resources. The right thing to do is to call functions that wake the waiting threads. Link: Cc: Andrew Clayton Signed-off-by: Alejandro Colomar --- man2/sched_yield.2 | 5 ----- 1 file changed, 5 deletions(-) diff --git a/man2/sched_yield.2 b/man2/sched_yield.2 index bab0f9569..5e5b45a48 100644 --- a/man2/sched_yield.2 +++ b/man2/sched_yield.2 @@ -54,11 +54,6 @@ .SH NOTES it will continue to run after a call to .BR sched_yield (). .PP -Strategic calls to -.BR sched_yield () -can improve performance by giving other threads or processes -a chance to run when (heavily) contended resources (e.g., mutexes) -have been released by the caller. Avoid calling .BR sched_yield () unnecessarily or inappropriately -- 2.40.1