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 D0D97211A09 for ; Tue, 11 Aug 2026 01:49:10 +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=1786412951; cv=none; b=T7DR61/46fMBJo+fAjgFyqOFxAobjBSWagaW85Qmazx2aqFKjwNeTmthzgThTISnymUgmqtvYXPXIpvAgYr4s/D2i6c8qgECeuZpoZTaCYoYe3SS3alkjnGaXEBmpWXrTcQi/BMWLhx/h9KeZJ6shqE46HAUDHPKcV5a4kFmDYM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1786412951; c=relaxed/simple; bh=b+3Ko0KxESZp/ehQCC9J2JHOVDWQXDTQm8UmxEZW3TM=; h=Message-ID:Date:MIME-Version:Cc:Subject:To:References:From: In-Reply-To:Content-Type; b=bwzZLKJp658T7BqjmAF7D9IfZkGl+5slXvWeynK4TluQvmnbrulFG5uvDDzh2BiwTel4UqDjxP5Mm7LME0qko8FgseMcIsERWrnwtSwrs6A6AESqlfCRPc0ILcmkx4u5GD1u3bdmwwfSP3BX78MWtgtcPvG9z+RZJP4yem6VqZo= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=aYS6WtjT; 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="aYS6WtjT" Received: by smtp.kernel.org (Postfix) with ESMTPSA id A357B1F000E9; Tue, 11 Aug 2026 01:49:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1786412950; bh=fbQdEIkPKTw83MfJdf7DZIxef/pakG3anpSyXn5xx0g=; h=Date:Cc:Subject:To:References:From:In-Reply-To; b=aYS6WtjT+Vuk2zfrsAfGMOuSeC1lvGDww95hmcn05dM6Y71Weksp5ORA1mvtmPKae 5TD4DbUyPd9OQOOHvISZDS4+6F3fO5uMn7V0s97R+RK4rlOJTvDoQ5Tl+FrD6gI8Pb WJIFJ5sfX168uDDJC2GBr4GZFZAvU/2eK1ye3mAFdg0ZHPAthxDmtCgAq8bKg5Xnt+ Mg/3FTF8tZC75UaaPRzyMzeMbZpaoM2eeWywDaT4H/WNsogcmW2uCwgJ7Y9TTyx43W 0xv2mpGHrh0EWTsvY2WPyxoLM0r9RR0bx07T3OIk764BYgPxHHvf+NX8CdDzZ3btxw nXn4uGOLmEy3g== Message-ID: <26a8478c-e8e4-47a3-8ffa-6a0b0b3182eb@kernel.org> Date: Tue, 11 Aug 2026 09:49:07 +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 Subject: Re: [f2fs-dev] [PATCH 2/2] f2fs: call __add_ino_entry out of the eviction path To: Jaegeuk Kim , linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net References: <20260807220235.384637-1-jaegeuk@kernel.org> <20260807220235.384637-2-jaegeuk@kernel.org> Content-Language: en-US From: Chao Yu In-Reply-To: <20260807220235.384637-2-jaegeuk@kernel.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit On 8/8/26 06:02, Jaegeuk Kim via Linux-f2fs-devel wrote: > The f2fs_evict_inode() can be called during the direct reclaim path, but > __add_ino_entry requires allocating some memory. Since we don't need to > do that in that context, let's migrate it in other workqueue context. > > Signed-off-by: Jaegeuk Kim Reviewed-by: Chao Yu Thanks,