From: Dave Olien <dmo@osdl.org>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, axboe@suse.de
Subject: Re: Badness in as_completed_request warning
Date: Tue, 9 Sep 2003 09:44:11 -0700 [thread overview]
Message-ID: <20030909164411.GA16913@osdl.org> (raw)
In-Reply-To: <3F5D7B6A.70703@cyberone.com.au>
On Tue, Sep 09, 2003 at 05:04:10PM +1000, Nick Piggin wrote:
>
> Thanks Dave,
> Can you try this one? I can't reproduce the problem here as I don't have
> enough disks unfortunately. Thanks
>
> Nick
One of OSDL's reasons for existance is to arrange for Linux developers
to have access to larger hardware configurations. I'm sure you could
get a project machine here at OSDL to do testing of I/O scheduler
modifications, or other testing on a larger machine. Several other
kernel developers have project machines here at OSDL.
Look at the web page
http://www.osdl.org/lab_activities/be_an_associate.html
Fill out the web page form to get a login. send email to Cliffw@osdl.org
and me, and we'll see that it gets handled quickly.
You'd be able to ssh into a front-end machine here at OSDL. It would
give you serial console access to a test machine. You'd also be able
to power on/power off and reset the test machine, and ssh into the
test machine from that front-end.
Dave
prev parent reply other threads:[~2003-09-09 16:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-08 16:48 Badness in as_completed_request warning Dave Olien
2003-09-09 3:40 ` Nick Piggin
2003-09-09 6:12 ` Dave Olien
2003-09-09 7:04 ` Nick Piggin
2003-09-09 15:38 ` Dave Olien
2003-09-09 16:44 ` Dave Olien [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=20030909164411.GA16913@osdl.org \
--to=dmo@osdl.org \
--cc=akpm@osdl.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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