* YET another problem in committing old transactions
@ 2004-09-15 21:56 Vijayan Prabhakaran
0 siblings, 0 replies; only message in thread
From: Vijayan Prabhakaran @ 2004-09-15 21:56 UTC (permalink / raw)
To: mason, reiserfs-list; +Cc: reiser, vijayan
Hi,
There is one more problem in committing the old transactions.
In function reiserfs_flush_old_commits(), there is a condition that checks
if the current transaction is older than 30 seconds. Only if that
condition satisfies, the data is flushed to the disk. The condition looks
like:
if (blah blah blah &&
(now - SB_JOURNAL(p_s_sb)->j_trans_start_time) >
SB_JOURNAL_MAX_TRANS_AGE(p_s_sb))
{
/*flush the transaction by calling do_journal_end*/
}
Note: SB_JOURNAL_MAX_TRANS_AGE(p_s_sb) returns 30 seconds.
Now my question is this:
When does reiserfs flush the old uncommitted data ? Is it every 5 seconds
or every 30 seconds ?
If it is going to do it in every 5 seconds when the thread wakes up, why
do we have the condition for 30 seconds ? If the flush happens only every
30 seconds, why the thread calls reiserfs_flush_old_commits() every 5
seconds ?
Is there any reason for this discrepancy ?
Vijayan
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-09-15 21:56 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-09-15 21:56 YET another problem in committing old transactions Vijayan Prabhakaran
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.