From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 72DCD3FFD for ; Wed, 7 Jan 2026 03:33:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767756815; cv=none; b=kcfubyLmY6lnIAn3rLE1AQjJO/xKjfD5/i3l+krn1i3OZU8qetn9ymueMVqagohkxLi+vMgsQJGzrD3kUHsWlsHM22cC7QnBnjmXMGVm0/LAE14l479u49/icfhLaxI1VPRBOdXy7p6qQc7XtxhVvsusta3clAcq1QXqIIp/+F4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1767756815; c=relaxed/simple; bh=9wLdBMl9J4DS8hO/SDzAEIivmTkhRy+hggga6K/6R8w=; h=Content-Type:MIME-Version:Subject:From:Message-Id:Date:References: In-Reply-To:To:Cc; b=A1ACmUi8f2Kzid4qUREXyCFafT1ELqJmLsD0RzXovX7GeJy6tL1QoL/zV1Kq2hQj9bfG9dRtxEZe5dFAArHhmJo0RUyI+IWG1B4AQYw+peJgYGLLRypd90oBP4Fp4oUHINrwtec8X8DmCArvASggzJhQBjyGaN6z00C6tFwaHgA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=ZRYczZ7C; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="ZRYczZ7C" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 11174C4CEF7; Wed, 7 Jan 2026 03:33:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1767756815; bh=9wLdBMl9J4DS8hO/SDzAEIivmTkhRy+hggga6K/6R8w=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=ZRYczZ7CO1pMZ2SMouY7rYTJhFwRqbKXWThoJUZzjw3WTbE5DOiTn7IEYdYt+t1lk Rv4S5g+rcA99ne2hiUzx7BoXyH5wZplIJcuzH+YEgJoHh6/0+xGO92/MmKr44Lkyvn AHzzg+2XZAJ35P2npe2wdwoBTyTwSsJGsTJA4wsEy50HrbUMCpS4AsXQILY3LEPS8o B+2Gp16DeTP5tk8IucdbcbMpPB4pMv2kcTQoJyZX1ZVnVC7B+RAKQEvXUAt4FwUFRu h34m78R2AwpzI1MfpU1h9jIyJSwcPxRWsdcjI/1mm+MZJ32hPXGuQI2V5YZQYMTGbk OGTIIM34BinrQ== Received: from [10.30.226.235] (localhost [IPv6:::1]) by aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org (Postfix) with ESMTP id B5727380CEF5; Wed, 7 Jan 2026 03:30:13 +0000 (UTC) Content-Type: text/plain; charset="utf-8" Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [f2fs-dev] [PATCH 01/14] f2fs: add lock elapsed time trace facility for f2fs rwsemphore From: patchwork-bot+f2fs@kernel.org Message-Id: <176775661252.2218650.8734034218364835852.git-patchwork-notify@kernel.org> Date: Wed, 07 Jan 2026 03:30:12 +0000 References: <20260104020729.1064529-1-chao@kernel.org> In-Reply-To: <20260104020729.1064529-1-chao@kernel.org> To: Chao Yu Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net Hello: This series was applied to jaegeuk/f2fs.git (dev) by Jaegeuk Kim : On Sun, 4 Jan 2026 10:07:16 +0800 you wrote: > This patch adds lock elapsed time trace facility for f2fs rwsemphore. > > If total elapsed time of critical region covered by lock exceeds a > threshold, it will print tracepoint to dump information of lock related > context, including: > - thread information > - CPU/IO priority > - lock information > - elapsed time > - total time > - running time (depend on CONFIG_64BIT) > - runnable time (depend on CONFIG_SCHED_INFO and CONFIG_SCHEDSTATS) > - io sleep time (depend on CONFIG_TASK_DELAY_ACCT and > /proc/sys/kernel/task_delayacct) > - other time (by default other time will account nonio sleep time, > but, if above kconfig is not defined, other time will > include runnable time and/or io sleep time as wll) > > [...] Here is the summary with links: - [f2fs-dev,01/14] f2fs: add lock elapsed time trace facility for f2fs rwsemphore https://git.kernel.org/jaegeuk/f2fs/c/79b3cebc70fc - [f2fs-dev,02/14] f2fs: sysfs: introduce max_lock_elapsed_time https://git.kernel.org/jaegeuk/f2fs/c/e4b75621fc43 - [f2fs-dev,03/14] f2fs: trace elapsed time for cp_rwsem lock https://git.kernel.org/jaegeuk/f2fs/c/66e9e0d55d11 - [f2fs-dev,04/14] f2fs: trace elapsed time for node_change lock https://git.kernel.org/jaegeuk/f2fs/c/f9f93602512b - [f2fs-dev,05/14] f2fs: trace elapsed time for node_write lock https://git.kernel.org/jaegeuk/f2fs/c/bb28b66875cc - [f2fs-dev,06/14] f2fs: trace elapsed time for gc_lock lock (no matching commit) - [f2fs-dev,07/14] f2fs: trace elapsed time for cp_global_sem lock https://git.kernel.org/jaegeuk/f2fs/c/ce9fe67c9cdb - [f2fs-dev,08/14] f2fs: trace elapsed time for io_rwsem lock https://git.kernel.org/jaegeuk/f2fs/c/67972c2b8974 - [f2fs-dev,09/14] f2fs: clean up w/ __f2fs_schedule_timeout() https://git.kernel.org/jaegeuk/f2fs/c/b5da276ae6ab - [f2fs-dev,10/14] f2fs: fix to use jiffies based precision for DEFAULT_SCHEDULE_TIMEOUT https://git.kernel.org/jaegeuk/f2fs/c/da90b6715567 - [f2fs-dev,11/14] f2fs: fix timeout precision of f2fs_io_schedule_timeout_killable() https://git.kernel.org/jaegeuk/f2fs/c/6fa116053951 - [f2fs-dev,12/14] f2fs: rename FAULT_TIMEOUT to FAULT_ATOMIC_TIMEOUT https://git.kernel.org/jaegeuk/f2fs/c/7a127c80b0ee - [f2fs-dev,13/14] f2fs: introduce FAULT_LOCK_TIMEOUT https://git.kernel.org/jaegeuk/f2fs/c/c56254e2e042 - [f2fs-dev,14/14] f2fs: sysfs: introduce inject_lock_timeout https://git.kernel.org/jaegeuk/f2fs/c/d36de29f4bb5 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html