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 E9DA4C38145 for ; Thu, 8 Sep 2022 08:36:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230475AbiIHIgi (ORCPT ); Thu, 8 Sep 2022 04:36:38 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36750 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229484AbiIHIgd (ORCPT ); Thu, 8 Sep 2022 04:36:33 -0400 X-Greylist: delayed 443 seconds by postgrey-1.37 at lindbergh.monkeyblade.net; Thu, 08 Sep 2022 01:36:31 PDT Received: from forward107j.mail.yandex.net (forward107j.mail.yandex.net [5.45.198.252]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EF74CDFF67 for ; Thu, 8 Sep 2022 01:36:31 -0700 (PDT) Received: from forward503j.mail.yandex.net (forward503j.mail.yandex.net [IPv6:2a02:6b8:0:801:2::113]) by forward107j.mail.yandex.net (Yandex) with ESMTP id BC6BF887600; Thu, 8 Sep 2022 11:28:35 +0300 (MSK) Received: from vla1-b7b6154c4cfd.qloud-c.yandex.net (vla1-b7b6154c4cfd.qloud-c.yandex.net [IPv6:2a02:6b8:c0d:3495:0:640:b7b6:154c]) by forward503j.mail.yandex.net (Yandex) with ESMTP id 851291DAEF93; Thu, 8 Sep 2022 11:28:35 +0300 (MSK) Received: by vla1-b7b6154c4cfd.qloud-c.yandex.net (smtp/Yandex) with ESMTPSA id lcmUcd9y5j-SXhq3kDm; Thu, 08 Sep 2022 11:28:35 +0300 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client certificate not present) X-Yandex-Fwd: 1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ya.ru; s=mail; t=1662625715; bh=SR28xl9TqG4sh99CnRD+CmQIr/ApB1Bmm4ByGm5C2b8=; h=From:In-Reply-To:Cc:Date:References:To:Subject:Message-ID; b=reuNp+lLBN8mo7vsvboOao24yPThnisLtpARlors6+zExuM9d4AfyJHR8LS1XDqsJ rPuXHIaXaFqC3yAx31fnNcxcSIda6y3EWCCZA2Oh4KGW7dkivmwwMJUH0wgY3T2Ycf HUAdIop7PBthImY0kkicoyutfqUatc3W+GyotBzc= Authentication-Results: vla1-b7b6154c4cfd.qloud-c.yandex.net; dkim=pass header.i=@ya.ru Message-ID: Date: Thu, 8 Sep 2022 11:28:31 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0 Subject: Re: [PATCH] jbd2: wake up journal waiters in FIFO order, not LIFO Content-Language: en-US To: Alexey Lyahkov , "Ritesh Harjani (IBM)" Cc: linux-ext4 , Theodore Ts'o , Andreas Dilger , Artem Blagodarenko References: <20220907165959.1137482-1-alexey.lyashkov@gmail.com> <20220908054611.vjcb27wmq4dggqmv@riteshh-domain> <20220908061153.dflgx7fjjav7pxyn@riteshh-domain> <5C1AAACF-5878-4812-8334-29A328B57A77@gmail.com> From: Andrew In-Reply-To: <5C1AAACF-5878-4812-8334-29A328B57A77@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-ext4@vger.kernel.org > Other logs have shown this thread can’t take a handle, but other threads able to do it many times. > Kernel detector don’t hit because thread have wakeup many times but it have seen T_LOCKED and go to sleep again. Also, the transactions are small because the workload is sync writes.