From: Theodore Tso <tytso@MIT.EDU>
To: Arjan van de Ven <arjan@infradead.org>
Cc: akpm@linux-foundation.org, jens.axboe@oracle.com,
linux-kernel@vger.kernel.org
Subject: Re: PATCH] fix potential latency issues in JBD's journal code
Date: Sun, 6 Jul 2008 08:20:58 -0400 [thread overview]
Message-ID: <20080706122058.GA26084@mit.edu> (raw)
In-Reply-To: <20080705223021.02735dc0@infradead.org>
On Sat, Jul 05, 2008 at 10:30:21PM -0700, Arjan van de Ven wrote:
> it's debatable. Because this submit-bh() will sometimes block... it
> wouldn't get IO started for that case. I think this is where I'd like
> Jens to say what he thinks the rules are; clearly the elevator needs to
> treat all of these guys as sync, but maybe the plugging should be ..
> flexible.
Stupid idea.... maybe the unplugging should be done on the wait side?
Has this been considered already?
- Ted
prev parent reply other threads:[~2008-07-06 12:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 2:29 PATCH] fix potential latency issues in JBD's journal code Arjan van de Ven
2008-07-05 5:00 ` Arjan van de Ven
2008-07-05 14:13 ` Theodore Tso
2008-07-05 15:18 ` Arjan van de Ven
2008-07-06 4:15 ` Theodore Tso
2008-07-06 5:30 ` Arjan van de Ven
2008-07-06 12:20 ` Theodore Tso [this message]
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=20080706122058.GA26084@mit.edu \
--to=tytso@mit.edu \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
/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