[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
<SEZPR06MB52691756B32BA90DBE82BDFDE8B22@SEZPR06MB5269.apcprd06.prod.outlook.com>
Date: Tue, 15 Apr 2025 08:56:03 +0000
From: 李扬韬 <frank.li@...o.com>
To: Qu Wenruo <quwenruo.btrfs@....com>, "clm@...com" <clm@...com>,
"josef@...icpanda.com" <josef@...icpanda.com>, "dsterba@...e.com"
<dsterba@...e.com>
CC: "linux-btrfs@...r.kernel.org" <linux-btrfs@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject:
回复: [PATCH] btrfs: remove BTRFS_REF_LAST from btrfs_ref_type
> History please.
Did you mean change commit msg to below?
Commit b28b1f0ce44c ("btrfs: delayed-ref: Introduce better documented delayed ref structures") introduce BTRFS_REF_LAST but never use it,
So let's remove it.
> The _LAST or _NR suffix can be utilized to do sanity checks, and this is not part of the on-disk format.
IIRC, delayed ref belongs to the extent tree memory kv cache.
> And if this exposed by some automatic tools, please also mention it.
I'm just looking at this code.
Thx,
Yangtao
Powered by blists - more mailing lists