From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 4EF3531F9A5 for ; Thu, 6 Aug 2026 02:43:25 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785984206; cv=none; b=oxxNfjfARtKopMtEqpm0B2fXnOMP66CngDa3GmK8NCEje49DqVpHzngYiwAAwlssmb7reim07Ex60p3MNMXaZ7BfvOZAoaEvSw84lKDbJLpApuXy5A9zOPaE5Qmnq51++ibXGiyXN0vhEVBnR13G7DHWnw7fY9EQ3jSXdOakKSI= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785984206; c=relaxed/simple; bh=j8KPZrsVkLY+3iGvY5EnoLLSEHvTIPVJYC7Qu8K6RnI=; h=Message-ID:Date:MIME-Version:Cc:Subject:To:References:From: In-Reply-To:Content-Type; b=kVusZ/A7U844jpDYWmobDRGZrrMiJ+9Fug64Z/oWVxuWHRnzZwhbpHqEOny+A93zMvB4+RPO95asVqNvJ3BVzCf+RHYK14DaHTvo/PxS73H7BklnIDWeGR/pgkK3p4QNUhJnvj6FprJqaJz2OVHhpm9WAkpJdZRoDlawFDU8XNI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=DmiSGt7v; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="DmiSGt7v" Received: by smtp.kernel.org (Postfix) with ESMTPSA id E43231F000E9; Thu, 6 Aug 2026 02:43:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1785984205; bh=3Dd4WfbZRD8AwlZNKwxkeecCbyQqQzv0Fu0d9QgTe5A=; h=Date:Cc:Subject:To:References:From:In-Reply-To; b=DmiSGt7v55DpXjqGKGwreEr/0/+HyWbb9No7WARKH1FD/9oSGysuVnDU+ZBRKoPYG mL/s8eMZsIzF0oX+22FOiRPWyEaz6sJy+7BNMJUom7/uWmDC6MntCCBV15rnSCaYqR Z8V5RZfioDe3M0I2nwd/yzK2FgLJQEg+p9v8/NPFUNkej+cgh8aTk3AR+/W0bBGf3L e/65ubd5IPsQ4NqaD5yn3CzK1WnYA6lY0BPQJ0yEO+qLVTohMamppJys2hmruVKvuY fLFmfX/LizRzruntnUvXHAl8LGv/Sbf6AqU/QBievmwugKAZ1eZkyS/JgQJno1ifIy qFfcmU11+EZXw== Message-ID: Date: Thu, 6 Aug 2026 10:43:22 +0800 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Cc: chao@kernel.org, Daeho Jeong Subject: Re: [f2fs-dev] [PATCH v7] f2fs: support dynamic reserve/release for device aliasing To: Daeho Jeong , linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com References: <20260806014813.1587003-1-daeho43@gmail.com> Content-Language: en-US From: Chao Yu In-Reply-To: <20260806014813.1587003-1-daeho43@gmail.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 8/6/26 09:48, Daeho Jeong wrote: > From: Daeho Jeong > > This patch adds a dynamic management feature to the existing device > aliasing functionality. It allows users to dynamically reserve or > release specific devices from the filesystem's free pool at runtime > through new ioctls. > > To support this, three new ioctls are introduced: > - F2FS_IOC_RESERVE_DEV_ALIAS: This reclaims the space occupied by a > device aliasing file. It first performs a capacity check, resets GC > victim information for the target range, marks the segments as in-use > to prevent new allocations, and then triggers GC to migrate existing > valid data out of the range. Finally, it reserves these blocks in the > SIT to effectively exclude the device from the usable capacity. > > - F2FS_IOC_RELEASE_DEV_ALIAS: This releases the reserved space of a > previously reserved device aliasing file. It truncates the blocks > associated with the file, which makes them available for general > filesystem allocation again. > > - F2FS_IOC_GET_DEV_ALIAS_STATUS: This retrieves the current aliasing > status of a device aliasing file, returning whether the file is > released (inactive alias) or reserved (active alias, with blocks > fully allocated on the device). > > Signed-off-by: Daeho Jeong Reviewed-by: Chao Yu Thanks,