From: Nick Piggin <piggin@cyberone.com.au>
To: azarah@gentoo.org
Cc: Jens Axboe <axboe@suse.de>, Linus Torvalds <torvalds@osdl.org>,
Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix IO hangs
Date: Sat, 06 Sep 2003 11:34:35 +1000 [thread overview]
Message-ID: <3F5939AB.5080804@cyberone.com.au> (raw)
In-Reply-To: <1062799434.11604.1.camel@nosferatu.lan>
Martin Schlemmer wrote:
>On Fri, 2003-09-05 at 19:04, Jens Axboe wrote:
>
>>On Fri, Sep 05 2003, Jens Axboe wrote:
>>
>>>>Jens, if insert_here is dead, there is no point to passing back a hint
>>>>because it can't get back to the elevator anyway.
>>>>
>>>>I'd very much like to kill insert_here and be done with it. If another
>>>>io scheduler comes along with a good use for it then the writers can
>>>>come up with an elegant solution ;) Hey, if they know a NO_MERGE return
>>>>means an insert will soon happen under the same lock, they could keep
>>>>it cached privately.
>>>>
>>>Agree, lets just kill it off.
>>>
>>Here's the patch that kills it and its associated logic off completely.
>>Nick, I'm not too sure what the logic was for stopping anticipation in
>>as_insert_request() (the insert_here tests were somewhat convoluted :),
>>I've added what I think makes most sense: stop anticipating if someone
>>puts a request at the head of the dispatch list.
>>
>>It also makes the *_insert_request strategies much easier to follow,
>>imo.
>>
>>
>
>Hmm, do not know if its just me, but I just got two processes (cp's)
>in D state. They did complete though, but throughput was not good.
>Any tips on getting it debugged ?
>
If they complete at all, then its very unlikely for them to be slowed
down (AS can do this a bit though). If you could get a comparison with
my patch that started the problems backed out it might tell me
something. Thanks.
prev parent reply other threads:[~2003-09-06 1:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-05 6:56 [PATCH] fix IO hangs Nick Piggin
2003-09-05 7:04 ` Jens Axboe
2003-09-05 7:16 ` Nick Piggin
2003-09-05 7:18 ` Jens Axboe
2003-09-05 8:31 ` Jens Axboe
2003-09-05 22:03 ` Martin Schlemmer
2003-09-06 1:34 ` Nick Piggin [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=3F5939AB.5080804@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=azarah@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.