From: "Miller, Mike (OS Dev)" <mike.miller@hp.com>
To: "Jeff Garzik" <jgarzik@pobox.com>
Cc: <alpm@odsl.org>, <axboe@suse.de>, <linux-kernel@vger.kernel.org>
Subject: RE: cciss updates for 2.6.6xxx [1/2]
Date: Wed, 7 Apr 2004 14:11:39 -0500 [thread overview]
Message-ID: <D4CFB69C345C394284E4B78B876C1CF105BC2012@cceexc23.americas.cpqcorp.net> (raw)
I like the idea of capping max commands based on the number of arrays. One problem is that we can add or remove a logical drive during runtime. How would Linux handle us reshuffling the max commands for each queue?
mikem
-----Original Message-----
From: Jeff Garzik [mailto:jgarzik@pobox.com]
Sent: Wednesday, April 07, 2004 11:34 AM
To: Miller, Mike (OS Dev)
Cc: alpm@odsl.org; axboe@suse.de; linux-kernel@vger.kernel.org
Subject: Re: cciss updates for 2.6.6xxx [1/2]
Miller, Mike (OS Dev) wrote:
> Yep, you're right. I just regurgitated the same code. I'll pull my head out and try again :(
The easiest thing to do may be to take your patch #1, and then add code
to clamp the per-queue outstanding-command (tag) depth to
1024 / n_arrays_found
at initialization time. Or perhaps s/n_arrays_found/max_arrays_per_hba/
I bet that's just a few additional lines of code, and should work...
Regards,
Jeff
next reply other threads:[~2004-04-07 19:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 19:11 Miller, Mike (OS Dev) [this message]
2004-04-07 19:42 ` cciss updates for 2.6.6xxx [1/2] Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2004-04-07 16:21 Miller, Mike (OS Dev)
2004-04-07 16:33 ` Jeff Garzik
2004-04-06 20:10 mikem
2004-04-07 16:14 ` Jeff Garzik
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=D4CFB69C345C394284E4B78B876C1CF105BC2012@cceexc23.americas.cpqcorp.net \
--to=mike.miller@hp.com \
--cc=alpm@odsl.org \
--cc=axboe@suse.de \
--cc=jgarzik@pobox.com \
--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).