From: "rae l" <crquan@gmail.com>
To: "Jeff Moyer" <jmoyer@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: iowait stability regressed from kernel 2.6.22 under heavy load of multi-thread aio writing/reading
Date: Wed, 16 Apr 2008 01:29:21 +0800 [thread overview]
Message-ID: <91b13c310804151029re71c227g281e2966f0d1728a@mail.gmail.com> (raw)
In-Reply-To: <x49k5izme80.fsf@segfault.boston.devel.redhat.com>
On Tue, Apr 15, 2008 at 9:37 PM, Jeff Moyer <jmoyer@redhat.com> wrote:
>
> "rae l" <crquan@gmail.com> writes:
[...]
>
> Why doesn't bisecting work? Can you provide your test code so others
> can verify your findings?
just small C programs that use multi pthread aio_write, will be pasted soon,
>
> > by the way, a question is how to guarantee a kernel not regress under
> > heavy multi-thread aio writing load? ltp project seems not give the
> > answer:
>
> Well, providing your test code would be a step closer to achieving this
> guarantee. If it is scriptable, then there is a chance we could
> integrate it into the aio-dio regression test suite:
>
> http://git.kernel.org/?p=linux/kernel/git/zab/aio-dio-regress.git;a=summary
this aio-dio-regress.git seems to use linux native aio system-call
interface(shipped with libaio) only? but the POSIX aio (shipped with
librt) implemented with pthread and pwrite system-call tests can also
be added, the librt is the most cases when refered to aio.
However, the test code will come soon.
--
Denis
next prev parent reply other threads:[~2008-04-15 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-11 9:17 iowait stability regressed from kernel 2.6.22 under heavy load of multi-thread aio writing/reading rae l
2008-04-15 13:37 ` Jeff Moyer
2008-04-15 17:29 ` rae l [this message]
2008-04-16 7:18 ` rae l
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=91b13c310804151029re71c227g281e2966f0d1728a@mail.gmail.com \
--to=crquan@gmail.com \
--cc=jmoyer@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).