From: kumon@flab.fujitsu.co.jp
To: Jens Axboe <axboe@suse.de>
Cc: kumon@flab.fujitsu.co.jp, linux-kernel@vger.kernel.org,
Dave Jones <davej@suse.de>, Andrea Arcangeli <andrea@suse.de>
Cc: kumon@flab.fujitsu.co.jp
Subject: Re: [PATCH] livelock in elevator scheduling
Date: Wed, 22 Nov 2000 19:59:38 +0900 [thread overview]
Message-ID: <200011221059.TAA03907@asami.proc.flab.fujitsu.co.jp> (raw)
In-Reply-To: <20001121112836.B10007@suse.de>
In-Reply-To: <200011210838.RAA27382@asami.proc.flab.fujitsu.co.jp> <20001121112836.B10007@suse.de>
Jens Axboe writes:
> I'd be very interested if you could repeat your test with my
> block patch applied. It has, among other things, a more fair (and
> faster) insertion.
>
> *.kernel.org/pub/linux/kernel/people/axboe/patches/2.4.0-test11/blk-11.bz2
This patch fixes the "DoS" behavior of the current queuing mechanism.
Even if I set the "pass-over" values to very large number (1000000) it
stably runs.
Thank you for your patch.
>From my understanding, passover is an option of the elevator
scheduling to prioritize long waiting requests for improving online
responses. In that test, passover value setting doesn't affect the
benchmark number, which is probable.
Will the patch is included in the next kernel?
BTW,
The major performance difference between test1 and test2 was caused by
whether the hard_dirty_limit is hit or not.
The current Linux has a lot of difficult to set parameters in
/proc/sys.
Once a system goes beyond some settable limits, the system behavior
changes so sharp. Bdf_prm.nrfract in fs/buffer.c is one of the
difficult parameters. I hope a tool to monitor or set these value.
--
Computer Systems Laboratory, Fujitsu Labs.
kumon@flab.fujitsu.co.jp
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-22 11:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 8:38 kumon
2000-11-21 10:28 ` Jens Axboe
2000-11-21 11:30 ` kumon
2000-11-21 11:36 ` Jens Axboe
2000-12-02 0:22 ` Russell Cattelan
2000-12-02 15:42 ` Jens Axboe
2000-12-04 23:25 ` Russell Cattelan
2000-12-05 1:38 ` Russell Cattelan
2000-12-05 23:01 ` Jens Axboe
2000-12-06 0:53 ` Russell Cattelan
2000-11-21 12:39 ` kumon
2000-11-21 13:01 ` Jens Axboe
2000-11-22 6:08 ` kumon
2000-11-22 10:59 ` kumon [this message]
2000-11-22 15:50 ` davej
[not found] <200011210828.RAA27311@asami.proc.flab.fujitsu.co.jp>
2000-11-21 15:12 ` Andrea Arcangeli
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=200011221059.TAA03907@asami.proc.flab.fujitsu.co.jp \
--to=kumon@flab.fujitsu.co.jp \
--cc=andrea@suse.de \
--cc=axboe@suse.de \
--cc=davej@suse.de \
--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®