[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20241002130004.69010-4-yizhou.tang@shopee.com>
Date: Wed, 2 Oct 2024 21:00:04 +0800
From: Tang Yizhou <yizhou.tang@...pee.com>
To: willy@...radead.org,
akpm@...ux-foundation.org,
chandan.babu@...cle.com
Cc: linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org,
linux-xfs@...r.kernel.org,
Tang Yizhou <yizhou.tang@...pee.com>
Subject: [PATCH 3/3] xfs: Fix comment of xfs_buffered_write_iomap_begin()
From: Tang Yizhou <yizhou.tang@...pee.com>
Since macro MAX_WRITEBACK_PAGES has been removed from the writeback
path, change MAX_WRITEBACK_PAGES to the actual value of 1024.
Signed-off-by: Tang Yizhou <yizhou.tang@...pee.com>
---
fs/xfs/xfs_iomap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/xfs/xfs_iomap.c b/fs/xfs/xfs_iomap.c
index 1e11f48814c0..bb4018395b6e 100644
--- a/fs/xfs/xfs_iomap.c
+++ b/fs/xfs/xfs_iomap.c
@@ -1097,7 +1097,7 @@ xfs_buffered_write_iomap_begin(
end_fsb = imap.br_startoff + imap.br_blockcount;
} else {
/*
- * We cap the maximum length we map here to MAX_WRITEBACK_PAGES
+ * We cap the maximum length we map here to 1024
* pages to keep the chunks of work done where somewhat
* symmetric with the work writeback does. This is a completely
* arbitrary number pulled out of thin air.
--
2.25.1
Powered by blists - more mailing lists