From: "Oliver Pinter" <oliver.pntr@gmail.com>
To: "Jeff Moyer" <jmoyer@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OP] v2.6.22.22-op1
Date: Thu, 1 May 2008 17:14:17 +0200 [thread overview]
Message-ID: <6101e8c40805010814rf64d402l1a9da0c3e22b9668@mail.gmail.com> (raw)
In-Reply-To: <x49fxt2axns.fsf@segfault.boston.devel.redhat.com>
On 5/1/08, Jeff Moyer <jmoyer@redhat.com> wrote:
> <oliver@zipernowsky.hu> writes:
>
> > I announced the v2.6.22.22-op1 "stable" kernel.
>
> > fs/aio.c | 23 ++++++++++++-----------
>
> > Jeff Moyer (1):
> > aio: account I/O wait time properly
>
> This version of the patch introduced a regression for UML. It was
> seeing 100% iowait time when it wasn't waiting on any I/O. There was a
> follow-up patch which did the io_schedule conditionally, see commit id:
>
> e00ba3dae077f54cfd2af42e939a618caa7a3bca
>
> Cheers,
>
> Jeff
>
> > diff --git a/fs/aio.c b/fs/aio.c
> > index dbe699e..b3419c5 100644
> > --- a/fs/aio.c
> > +++ b/fs/aio.c
> > @@ -1170,7 +1171,7 @@ retry:
> > ret = 0;
> > if (to.timed_out) /* Only check after read evt */
> > break;
> > - schedule();
> > + io_schedule();
> > if (signal_pending(tsk)) {
> > ret = -EINTR;
> > break;
>
hmm, this is the relevant code in 2.6.22:
----8<-------------->8-----
if (min_nr <= i)
break;
ret = 0;
if (to.timed_out) /* Only check after read evt */
break;
schedule(); <-----------
if (signal_pending(tsk)) {
ret = -EINTR;
break;
}
/*ret = aio_read_evt(ctx, &ent);*/
----8<-------------->8-----
--
Thanks,
Oliver
next prev parent reply other threads:[~2008-05-01 15:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 14:32 oliver
2008-05-01 14:47 ` Jeff Moyer
2008-05-01 14:56 ` Oliver Pinter
2008-05-01 15:14 ` Oliver Pinter [this message]
2008-05-01 15:17 ` Oliver Pinter
2008-05-01 14:43 oliver
2008-05-01 15:01 ` Gabriel C
2008-05-01 15:08 ` Oliver Pinter
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=6101e8c40805010814rf64d402l1a9da0c3e22b9668@mail.gmail.com \
--to=oliver.pntr@gmail.com \
--cc=jmoyer@redhat.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
all inboxes | Powered by JetHome®