From: Miles Lane <miles@speakeasy.org>
To: Jens Axboe <axboe@suse.de>
Cc: Rui Sousa <rsousa@grad.physics.sunysb.edu>,
Rik van Riel <riel@conectiva.com.br>,
linux-kernel@vger.kernel.org
Subject: Re: Blocked processes <=> Elevator starvation?
Date: Sun, 29 Oct 2000 11:21:35 -0800 [thread overview]
Message-ID: <39FC78BF.90607@speakeasy.org> (raw)
In-Reply-To: <20001027134603.A513@suse.de> <Pine.LNX.4.21.0010280408520.1157-100000@localhost.localdomain> <20001027202710.A825@suse.de>
Jens Axboe wrote:
> On Sat, Oct 28 2000, Rui Sousa wrote:
>
>> After adding
>>
>> #define ELEVATOR_HOLE_MERGE 3
>>
>> to linux/include/linux/elevator.h it compiled ok.
>
>
> Oops sorry, I'm on the road so the patch was extracted
> from my packet writing tree (and not my regular tree).
>
>
>> There were still some stalls but they only lasted a couple of
>> seconds. The patch did make a difference and for the better.
>
>
> Ok, still needs a bit of work. Thanks for the feedback.
Have you resolved this problem completely, now?
I am testing the USB Storage support with my ORB backup
drive. When I run:
dd if=/dev/zero of=/dev/sda bs=1k count=2G
The drive gets data quickly for about thirty seconds.
Then the throughput drops off to about ten percent
of its previous transfer rate. This dropoff appears to
be due to conflict over accessing filesystems. Specifically,
I have USB_STORAGE_DEBUG enabled, which shoots a ton of
debugging output into my kernel log. When the throughput
to the ORB drive falls off, all writing to the syslog
ceases. At least, that's what "tail -f" shows.
I would be happy to test any patches you have for this
problem.
I hope this helps,
Miles
-
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-10-29 18:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0010080105520.22898-100000@duckman.distro.conectiva>
2000-10-27 16:22 ` Blocked processes <=> Elevator starvation? Rui Sousa
2000-10-27 16:31 ` Rik van Riel
2000-10-27 20:46 ` Jens Axboe
2000-10-28 3:14 ` Rui Sousa
2000-10-28 3:27 ` Jens Axboe
2000-10-29 19:21 ` Miles Lane [this message]
2000-10-29 22:45 ` Jens Axboe
2000-10-29 22:20 ` Jeff V. Merkey
2000-10-31 0:47 ` Miles Lane
2000-11-03 19:04 ` Jens Axboe
2000-11-06 1:03 ` Giuliano Pochini
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=39FC78BF.90607@speakeasy.org \
--to=miles@speakeasy.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
--cc=rsousa@grad.physics.sunysb.edu \
/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