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: Tue, 21 Nov 2000 20:30:33 +0900 [thread overview]
Message-ID: <200011211130.UAA27961@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:
> > Problem:
> > Current elevator_linus() traverses the I/O requesting queue from the
> > tail to top. And when the current request has smaller sector number
> > than the request on the top of queue, it is always placed just after
> > the top.
> > This means, if requests in some sector range are continuously
> > generated, a request with larger sector number is always places at the
> > last and has no chance to go to the front. e.g. it is not scheduled.
>
> Believe it or not, but this is intentional. In that regard, the
> function name is a misnomer -- call it i/o scheduler instead :-)
I never believe it intentional. If it is true, the current kernel
will be suffered from a kind of DOS attack. Yes, actually I'm a
victim of it.
By Running ZD's ServerBench, not only the performance down, but my
machine blocks all commands execution including /bin/ps, /bin/ls... ,
and those are not ^C able unless the benchmark is stopped. Those
commands are read from disks but the requests are wating at the end of
I/O queue, those won't be executed.
Anyway, I'll try your patch.
--
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-21 12:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 8:38 [PATCH] livelock in elevator scheduling kumon
2000-11-21 10:28 ` Jens Axboe
2000-11-21 11:30 ` kumon [this message]
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
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=200011211130.UAA27961@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;
as well as URLs for NNTP newsgroup(s).