From 9ebc6e3c2de5ad15e7b95c22adbc76bc334ff2cb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Axel=20D=C3=B6rfler?= Date: Thu, 20 Oct 2005 09:29:40 +0000 Subject: [PATCH] Added a comment on what kind of functionality we need from the caching layer one day. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@14442 a95241bf-73f2-0310-859d-f6bbb57e9c96 --- src/add-ons/kernel/file_systems/bfs/Journal.cpp | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/src/add-ons/kernel/file_systems/bfs/Journal.cpp b/src/add-ons/kernel/file_systems/bfs/Journal.cpp index 439673e739..4a434c6e18 100644 --- a/src/add-ons/kernel/file_systems/bfs/Journal.cpp +++ b/src/add-ons/kernel/file_systems/bfs/Journal.cpp @@ -711,6 +711,13 @@ Journal::Lock(Transaction *owner) fOwner = owner; + // ToDo: we need a way to find out how big the current transaction is; + // we need to be able to either detach the latest sub transaction on + // demand, as well as having some kind of fall back plan in case the + // sub transaction itself grows bigger than the log. + // For that, it would be nice to have some call-back interface in the + // cache transaction API... + if (fUnwrittenTransactions > 0) { // start a sub transaction cache_start_sub_transaction(fVolume->BlockCache(), fTransactionID);