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 D74213C65FD; Sun, 17 May 2026 17:26:33 +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=1779038793; cv=none; b=dR0xkuVbkRnF/0w7wsWHLTqqD08J1r1Ehm847ulZ9tsLxsc1SXmecdgHRJ6Ht3W/upx6yabKEA9bzSi9UZ8yhq0JOwz0E25hMzkrtIipr7KejGx8MdVSkWgBfky0Du/JyNg1bzlMAg/vwHCVhMyayHTj01MwTg+NnUbkS+4PM40= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779038793; c=relaxed/simple; bh=lGKadVHrKNT6CmfLVM9JxMsWPtA5cHWet/JGmKOuSG4=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=tCId5nV8LzX/kGUcT5/uCRXAZ6Vd/IUmerY/1bukMRO3B78ueYpgH7hsyDr/QGZfuHcExlA3aBSPoZzjcd/QKy0KaUw5ZT8aGzyrqId6b93h/9g+YPrI48WtUi98+nkC+WnoSYJlFTnyKQy4jo0U56enRZXkqI5Y7BgM01esswU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=V14Teuym; 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="V14Teuym" Received: by smtp.kernel.org (Postfix) with ESMTPSA id C912EC2BCB8; Sun, 17 May 2026 17:26:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1779038793; bh=lGKadVHrKNT6CmfLVM9JxMsWPtA5cHWet/JGmKOuSG4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=V14Teuym/BTICjj06GX/CguKshYW0qhHPZ8mASyUXBhZ+kn/vrv8I9k7og2EsFjsU oE56s0i4z9OjB0cy8uThGQwgfkpB8ck5evKRR1NwuP6oCDKmGxm9MM/DzljbJ5zi9o 4UJS9phIW/XSrkxAuFw9j9UnM+VcfDmcZOoQRdjxkc78eqflUyH5ygIUEWcCbq1O7x LcG+eiRefLnbIaAVe4zZbPwxZ11CeNCojW2ILF5inBqaGqRutMrwzY30q2kyIIefI0 QCM6/NHPVCxf09NczrpQ9fFai4sB6zOPdIjTI8eed5oo38NauriLcUSfhV7rdKv3fI NQhO6ltep+iLA== Date: Sun, 17 May 2026 20:26:25 +0300 From: Mike Rapoport To: Pasha Tatashin Cc: linux-kselftest@vger.kernel.org, shuah@kernel.org, akpm@linux-foundation.org, linux-mm@kvack.org, skhan@linuxfoundation.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, corbet@lwn.net, dmatlack@google.com, kexec@lists.infradead.org, pratyush@kernel.org, skhawaja@google.com, graf@amazon.com Subject: Re: [PATCH v2 04/10] liveupdate: add support for linked-block serialization Message-ID: References: <20260514222628.931312-1-pasha.tatashin@soleen.com> <20260514222628.931312-5-pasha.tatashin@soleen.com> Precedence: bulk X-Mailing-List: linux-doc@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260514222628.931312-5-pasha.tatashin@soleen.com> On Thu, May 14, 2026 at 10:26:22PM +0000, Pasha Tatashin wrote: > Introduce a linked-block serialization mechanism for LUO state. > > Previously, LUO used contiguous memory blocks for serializing sessions > and files, which imposed limits on the total number of items that could > be preserved across a live update. > > This commit adds the infrastructure for a more flexible, block-based > approach where serialized data is stored in a chain of linked blocks. > This is a preparatory step to allow an unlimited number of > luo_sessions and luo_files to be preserved. Shouldn't it be a part of KHO? > Signed-off-by: Pasha Tatashin > --- > Documentation/core-api/liveupdate.rst | 8 + > include/linux/kho/abi/luo.h | 22 ++ > kernel/liveupdate/Makefile | 1 + > kernel/liveupdate/luo_block.c | 388 ++++++++++++++++++++++++++ > kernel/liveupdate/luo_internal.h | 57 ++++ > 5 files changed, 476 insertions(+) > create mode 100644 kernel/liveupdate/luo_block.c -- Sincerely yours, Mike.