From: Alex Tomas <alex@clusterfs.com>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Alex Tomas <alex@clusterfs.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
"ext2-devel@lists.sourceforge.net"
<ext2-devel@lists.sourceforge.net>, Andrew Morton <akpm@osdl.org>
Subject: Re: [Ext2-devel] [PATCH] JBD: fix against journal overflow
Date: Mon, 24 Jan 2005 20:47:35 +0300 [thread overview]
Message-ID: <m3llaien2g.fsf@bzzz.home.net> (raw)
In-Reply-To: <1106588589.2103.116.camel@sisko.sctweedie.blueyonder.co.uk> (Stephen C. Tweedie's message of "Mon, 24 Jan 2005 17:43:09 +0000")
>>>>> Stephen C Tweedie (SCT) writes:
SCT> I don't see how that "limit" is relevant here. wbuf is nothing but the
SCT> size of the IO batches we pass to ll_rw_block() during that commit
SCT> phase. j_free affects the total size of space the *entire* commit has
SCT> to run into, and (as akpm has commented with a big marker beside it)
SCT> start_this_handle() reserves a *lot* of headroom for the extra space
SCT> that may be needed for transaction metadata.
/* If there's no more to do, or if the descriptor is full,
let the IO rip! */
if (bufs == ARRAY_SIZE(wbuf) ||
commit_transaction->t_buffers == NULL ||
space_left < sizeof(journal_block_tag_t) + 16) {
....
/* Force a new descriptor to be generated next
time round the loop. */
descriptor = NULL;
bufs = 0;
------------------------^^^^^^^^^^^^^^^^^^^
SCT> Have you really seen this patch make a difference in testing?
of course
next prev parent reply other threads:[~2005-01-24 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 15:32 Alex Tomas
2005-01-24 17:43 ` [Ext2-devel] " Stephen C. Tweedie
2005-01-24 17:47 ` Alex Tomas [this message]
2005-01-24 18:18 ` Stephen C. Tweedie
2005-01-24 19:27 ` Alex Tomas
2005-01-24 20:42 ` Stephen C. Tweedie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3llaien2g.fsf@bzzz.home.net \
--to=alex@clusterfs.com \
--cc=akpm@osdl.org \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sct@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®